Add commands to usage report #1299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds tracking for new command executions in the usage report:
config_oidc: Tracks the number of times the config command is executed with OIDC.config: Track the amount of times JFrog server has been configured. ( Notice this includes Add or Edit operation for both OIDC and non OIDC )rt_build_publish_auto: Tracks instances when builds are automatically published.Tracking is enabled by setting specific environment variables in the
setup-cli-action, which the CLI then reads to report usage data.Note: The config command usage report only includes cases where
config_oidcis used, as it is more useful to differentiate between "add" and "edit" operations rather than general config usage.