Dealing with orphan resources #101
MikhailGordienk
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In general, creating a resource requires several steps: catalog, offer, representation, etc. Those are independent calls. In case something goes wrong with catalog creation or with rule association, what is the "recover" strategy?
I can think of some special tags to mark those entities that are not yet "working", like empty catalogs, rules not attached to any contract, etc. This way it would be possible to search for them and clean them up.
This might not be necessary if the only way to interact with a connector is via the Config Manager, but I am thinking about managing resources from other applications via REST API.
Beta Was this translation helpful? Give feedback.
All reactions