Schema service upgrades may be blocked by schemas created in private tenants.
Currently, the creation of system schema may be blocked by the private internal schema in a private tenant. If schema initially were created in the private tenant.
Cons of current flow:
- Easy to break bootstrapping, it will fail with errors like:
Error with kind osdu:wks:master-data--ConnectedSourceDataJob:1.3.0: Message: Update/Create failed because schema id is present in another tenant
- It's not possible to fix it through API, since Schema doesn't have a DELETE endpoint.
Proposal:
- There is none for now.
Additional info: