Asset name should be validated against a specific service not across services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Community App Catalog |
New
|
Undecided
|
Unassigned |
Bug Description
Currently, it seems like, asset name is required to be unique across the schema. However, this can be a problem for two catalog services with similar offerings, for example heat and tosca. Since both services cater to templates, it is common that both can offer a similar type of templates.
For example, Hello World template where 'Hello World' is an appropriate asset name to both services. But currently, it doesn't allow user to set the same name.
2016-03-07 19:58:09.693 | Traceback (most recent call last):
2016-03-07 19:58:09.693 | File "openstack_
2016-03-07 19:58:09.693 | 'openstack_
2016-03-07 19:58:09.694 | File "openstack_
2016-03-07 19:58:09.694 | self.fail(
2016-03-07 19:58:09.694 | File "/home/
2016-03-07 19:58:09.694 | raise self.failureExc
2016-03-07 19:58:09.694 | AssertionError: Duplicate asset name: Hello World
http://
The solution could to check uniqueness of name within a particular service, not across services, for a better naming and display on http://
summary: |
- Asset name should validate against service for uniqueness + Asset name should be validated against a specific service not across + services |
description: | updated |