This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A schema config is linked to a credential definition and/or a trusted issuer. We had a startup job that deleted the default (read only) schemas on each startup regardless of any linked objects. As there were no db constraints child objects were referencing none existing objects resulting in joins without a result. I removed the read only attributes and added constraints. Schemas are only added if they do not exist already, and it is not possible to delete a schema if it is still referenced somewhere.