-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
front-door extension can not find existing front door resources #5170
Comments
Thank you for your feedback. This has been routed to the support team for assistance. |
route to CXP team |
@petersladek Apologies for the late reply. Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update. |
@petersladek While I ran the command Could you please follow the below action plan and check if that helps ? Plan 1:
Plan 2: |
That is not working for me. However I found out the root cause. |
fixes Azure/issues/5170 For managing Azure Front Door Standard/Premium, please refer https://docs.microsoft.com/en-us/cli/azure/afd?view=azure-cli-latest. For classical Azure Front Door, please refer https://docs.microsoft.com/en-us/cli/azure/network/front-door?view=azure-cli-latest.
@petersladek Thanks for the update and sharing the feedback. I have created the above PR to update our documentation. It is currently under review. In the meantime if you have any questions, please feel free to ask. |
Related command
Extension name (the extension in question)
front-door
Description of issue (in as much detail as possible)
I was trying to use AZ cli to execute some command against existing front-door, but found out that front-door extension is unable to locate any FD resources by name or resource id for any command I tried. I was getting (ResourceNotFound) error. Then found out that executing "az network front-door list" returns empty array. I tried multiple subscriptions containing front door resource, access with different accounts, using AZ cli both on windows and linux, and the result was the same.
Update: I am using latest version 1.0.16 of the front-door extension.
The text was updated successfully, but these errors were encountered: