In case of deploy error there is no rollback #1236
Replies: 2 comments
-
|
Hi, @augustinluca , Regarding the request for state management and rollback (similar to tools like Terraform), we acknowledge this is a powerful concept. Currently, the However, always evaluating future directions for this tool! We will track this idea as a feature request to see if state management features could be integrated or partially supported down the road. We've added your suggestion to our backlog for future consideration. |
Beta Was this translation helpful? Give feedback.
-
|
We're moving this feature request to a GitHub discussion to encourage broader collaboration and input from the community. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Description
If you use deploy option with whole yaml file, in case of any error during deploy, there is no rollback for already deployed components which may lead to inconsistent state of the tenant.
Expectation
Before actual deploy a schema validation or similar should be perform to reduce the possibility of having errors during deploy.
Reproduction
To test this scenario:
error: Problem running command import during stage processChanges when processing type clientGrants
error: Problem updating clientGrants {"id":"xxxxxxxxx","client_id":"xxxxxxxxxx","audience":"https://domain.com/api/v2/"}
ManagementApiError: Payload validation error: 'Additional properties not allowed: subject_type'.
Deploy CLI version
8.21
Node version
22
Beta Was this translation helpful? Give feedback.
All reactions