Support for Access Token Option in CLI Commands

[Silinde87]

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!

[bezoerb]

Hey @Silinde87,

sorry for the late reply.
We definitely can add support for passing the access token via CLI argument.

Setting the token as an environment variable should already work fine.
Just set CONTENTFUL_MANAGEMENT_TOKEN in your ci/cd pipeline

[bezoerb]

we should also improve the documentation to list the available environment variables:

• CONTENTFUL_SPACE_ID
• CONTENTFUL_ENVIRONMENT_ID
• CONTENTFUL_MANAGEMENT_TOKEN