-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
None
-
None
Currently, if we import a blueprint with no id of the Custom Repository, the import fails. We should be able to support this, as the ids of Custom Repositories do not match across accounts.
We should support importing Custom Repositories, but with the current design this is not possible.
After https://issues.redhat.com/browse/HMS-4445:
- let's wait for import/export endpoints
- use the endpoints when importing
- to discuss:
- at which point should we create Custom Repositories?
- how do we warn users that they already have the given repository with the same URL?
- how should we handle errors of blueprint importing, in case Custom Repositories were already successfully imported?