-
Bug
-
Resolution: Done
-
Undefined
-
None
-
0.3.0 [R4]
-
None
-
None
Description: Database Connection Object on the developer topology view loaded with random unique value
Expected Result:
Expecting the same behavior as 0.2.0, which is database connection name contains database instance name as prefix along with the unique string value
Actual Result:
DBSC has random unique string naming without instance name
Impact:
When we have two or more instances deployed on the same namespace/project, then DBSC has unique string name which impacts identifying the appropriate DBSC instances on Topology view
Screenshot:
Add to Topology screen with Instance name
Once the instance deployed on Topology screen, DBSC loaded with unique name
- causes
-
DBAAS-968 address binding name length/usefulness issues
- Waiting