While we don't enforce global uniqueness for catalog names, we do need to make sure that we don't let people import the same catalog name from two different accounts because that would create a subject conflict. Doing this today probably results in a bad request with Synadia Cloud API rejecting the call because of this.
We should tell them the catalog name is not unique among the imports and reject the attempt.
We should do a check against the list of all previously shared catalogs when someone does a catalog new, and warn them that it won't be sharable because of the name.
When someone attempts to share a catalog, reject it if it has already been shared previously
While we don't enforce global uniqueness for catalog names, we do need to make sure that we don't let people import the same catalog name from two different accounts because that would create a subject conflict. Doing this today probably results in a bad request with Synadia Cloud API rejecting the call because of this.
new, and warn them that it won't be sharable because of the name.