-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[CHORE] add azure cloud shell option for cli installation #32152
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
base: master
Are you sure you want to change the base?
[CHORE] add azure cloud shell option for cli installation #32152
Conversation
Preview links (active after the
|
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.
Looks good--thanks! Just a few tiny suggestions.
#### Azure Cloud Shell | ||
To use the Datadog CLI in [Azure Cloud Shell][203], open cloud shell and use `npx` to run the cli directly. Set your api key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the cli: |
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.
To use the Datadog CLI in [Azure Cloud Shell][203], open cloud shell and use `npx` to run the cli directly. Set your api key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the cli: | |
To use the Datadog CLI in [Azure Cloud Shell][203], open cloud shell and use `npx` to run the CLI directly. Set your API key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the CLI: |
```shell | ||
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | ||
``` |
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.
What do you think about putting the export commands here as well?
```shell | |
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | |
``` | |
```shell | |
export DD_API_KEY=<DATADOG_API_KEY> | |
export DD_SITE=<DATADOG_SITE> | |
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | |
``` |
|
||
#### Azure Cloud Shell | ||
|
||
To use the Datadog CLI in [Azure Cloud Shell][603], open cloud shell and use `npx` to run the cli directly. Set your api key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the cli: |
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.
To use the Datadog CLI in [Azure Cloud Shell][603], open cloud shell and use `npx` to run the cli directly. Set your api key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the cli: | |
To use the Datadog CLI in [Azure Cloud Shell][603], open cloud shell and use `npx` to run the CLI directly. Set your API key and site in the `DD_API_KEY` and `DD_SITE` environment variables, and then run the CLI: |
```shell | ||
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | ||
``` |
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.
```shell | |
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | |
``` | |
```shell | |
export DD_API_KEY=<DATADOG_API_KEY> | |
export DD_SITE=<DATADOG_SITE> | |
npx @datadog/datadog-ci aas instrument -s <subscription-id> -g <resource-group-name> -n <app-service-name> | |
``` |
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes