Closed insertmike closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Please count my vote for support of undoing plan deprecation.
Problem Context
The current flow of the states of a plan for API in a Gravitee context is:
STAGING: Allowed to PUBLISH and CLOSE
PUBLISHED: Allowed to DEPRECATE and CLOSE
DEPRECATED: Allowed to CLOSE
CLOSED: Not allowed to change state
Behaviour
I can't find particular reason why Gravitee does not allow plans to be shifted from DEPRECATED back to STAGING and etc. There might be cases when this is required and at this point of time the only thing that can be done to achieve this is to:
Which process is itself redundant.
Possible Solution
Allow shifting of plans back the chain ( E.G DEPRECATED -> PUBLISHED )
Steps to Reproduce (for bugs)
Context