You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree that if it's only for change detection purpose, using an annotation makes more sense than including the version ID as part of the AWSSecret CRD itself.
Can we avoid each secret being created to include the key for
AWSVersionID
?We have a CRD that can only accept a single Key/Value and it is currently not compatible with AWSSecret CRD's
The text was updated successfully, but these errors were encountered: