ROX-29469: New check flagging use of deprecated fields in SecuredCluster CR #1081
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.
NOTE: Don't merge before ROX-29469.
New check flagging use of deprecated fields in SecuredCluster CR.
This PR pulls in StackRox CRDs, currently from the PR branch stackrox/stackrox#18494. That's also the reason for the huge size of this PR.
It depends on new
deprecated:"true"Go struct tags being added to our CRD types.This PR only focuses on SecuredCluster, but a similar check+tests for the Central PR shall follow, once this has passed review.
This is the first step towards ROX-29469, focusing on situations where the user has set deprecated fields in their CR.
A second step would be to introduce a new struct tag
"hasdefault"(or similar name), which works pretty much like the"deprecated"tag.