-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VAULT-24556: add secret syncs to vault operator usage output #25751
Conversation
Build Results: |
CI Results: |
@@ -242,6 +242,9 @@ func (c *OperatorUsageCommand) parseNamespaceCount(rawVal interface{}) (UsageRes | |||
return ret, errors.New("missing non_entity_tokens") | |||
} | |||
|
|||
// don't error if secret syncs are 0 | |||
ret.secretSyncs, _ = jsonNumberOK(counts, "secret_syncs") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, My question is unrelated to this PR but I am curious if there no possibility to have 0 distinct entities?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should make this comment clearer. The problem isn't that there are 0, it's that secret_syncs
isn't a key in the output. This could happen if your Vault CLI version is newer than your Vault server version.
No description provided.