-
Notifications
You must be signed in to change notification settings - Fork 173
Closed
Labels
Description
Checklist
- I have looked into the README and have not found a suitable solution or answer.
- I have looked into the documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have upgraded to the latest version of this tool and the issue still persists.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
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:
- retrieve tenant metadata with version 8.14 as example using yaml format
- do the deploy of exactly the same metadata.
- an error similar with below one will be thrown:
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'. - components that were already deployed up to this error are not reverted which may lead to inconsistent state of tenant.
Deploy CLI version
8.21
Node version
22