Only require the activeGate token scope if activeGates are used #1220
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.
The token checking logic only checked if the feature-flag is present or not, and in 0.9 it became default, so it always required it, even though you may not even want to deploy activeGates
How can this be tested?
Use a token without the
activeGateTokenManagement.create
scopeDeploy a dynakube without ActiveGates => should work
Deploy a dynakube with ActiveGates => should complain about the tokens
Checklist
[x] Unit tests have been updated/added