Skip to content
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

az batch pool | example links need to be escaped in reference content #8065

Open
dbradish-microsoft opened this issue Oct 7, 2024 · 2 comments
Labels
Batch bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team.

Comments

@dbradish-microsoft
Copy link
Contributor

dbradish-microsoft commented Oct 7, 2024

Describe the bug

Please see similar issue for Core command subgroup az batch account: Azure/azure-cli GH issue #29622


Describe the bug

Please escape these example links in source code so they are corrected in MicrosoftDocs/azure-docs-cli autogenerated reference content.

Example links are needed in reference examples, but they should to be escaped so that GitHub does not treat them like live URLs.

List of Extension links that need escaped:

File name Build error
latest/docs-ref-autogen/batch/pool.yml Link 'https://learn.microsoft.com/azure/virtual-' points to a learn site page that doesn't exist. Check the path or URL and update the link.

Related command

az batch pool

@dbradish-microsoft dbradish-microsoft added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Oct 7, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Oct 7, 2024

Thank you for opening this issue, we will look into it.

Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @mksuni, @bgklein, @mscurrell, @dpwatrous, @gingi, @paterasMSFT, @cRui861.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Batch bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants