Update TypeHandlerVersion to 7.0 for Windows command #27697
Conversation
This file contains hidden or 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
buraizu
added
the
under_review
|
Thanks, created DOCS-10168 to follow up on additional, potentially related updates |
|
Added other required parameters when running command. |
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.
What does this PR do? What is the motivation?
The latest typeHandlerVersion is 7.0. However, the command in our public doc is still using 5.0.
https://github.com/DataDog/azure-extension/blob/master/arc-windows-ui/Artifacts/MainTemplate.json#L36
https://docs.datadoghq.com/integrations/guide/powershell-command-to-install-azure-datadog-extension/?tab=windows
This confused some customers like the below. The Azure VM extension is being labelled as 5.0.0.0 even though it downloads the latest version of the agent.
https://datadog.zendesk.com/agent/tickets/2033184
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/descriptionnaming convention) and then add the following PR comment:Additional notes