Fix the FQN usage for applications
MuranoPL classes and packages should have globally unique FQNs to prevent potential name collisions when environment combines packages provided by different developers. A name of a package should be started with a reversed Internet domain name given that the domain is controlled by the developer of the package or class.
'io.murano' namespace should indicate that the package has been developed by the core murano team and should be reserved only to the system murano packages (such as the core library). Demo applications should be placed into 'com.example' namespace to indicate their example-only nature.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Tatiana Kholkina
- Direction:
- Needs approval
- Assignee:
- Tatiana Kholkina
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Tatiana Kholkina
- Completed by
- Tatiana Kholkina
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Update namespaces for k8s applications
Addressed by: https:/
Update namespaces for docker applications
Addressed by: https:/
Update namespaces for applications
Addressed by: https:/
Update namespace for DockerStandalon
Addressed by: https:/
Update namespaces for applications
Addressed by: https:/
Update namespaces for applications
Addressed by: https:/
Update namespaces for applications
Addressed by: https:/
Update namespaces for k8s applications
Addressed by: https:/
Update namespaces for k8s applications
Addressed by: https:/
Update namespaces for k8s applications
Addressed by: https:/
Update namespaces for docker applications
Addressed by: https:/
Update namespace for DockerStandalon
Addressed by: https:/
Update namespaces for docker applications
Addressed by: https:/
Update namespace for DockerStandalon
Addressed by: https:/
Update namespaces for docker applications
Addressed by: https:/
Update namespace for DockerStandalon
