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
While reviewing the available commands in the CLI, I noticed that there doesn't appear to be an option to pass the accessToken directly as a command-line argument.
Currently, I can configure the access token through config files to utilize the tool within a pipeline. However, I am concerned that this approach might inadvertently expose the access token if the config files are committed to the repository.
Would it be possible to add support for passing the access token directly as an option in the CLI commands? Alternatively, do you recommend a safer way to use an access token—such as leveraging environment variables—so it can be consumed securely within CLI commands?
Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
While reviewing the available commands in the CLI, I noticed that there doesn't appear to be an option to pass the accessToken directly as a command-line argument.
Currently, I can configure the access token through config files to utilize the tool within a pipeline. However, I am concerned that this approach might inadvertently expose the access token if the config files are committed to the repository.
Would it be possible to add support for passing the access token directly as an option in the CLI commands? Alternatively, do you recommend a safer way to use an access token—such as leveraging environment variables—so it can be consumed securely within CLI commands?
Thank you!
The text was updated successfully, but these errors were encountered: