az monitor scheduled-query create doesn't support an identity parameter #8364
Labels
Auto-Assign
Auto assign by bot
Azure CLI Team
The command of the issue is owned by Azure CLI team
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Monitor
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Describe the bug
Attempting to create a scheduled query using a Azure Resource Graph query results in an error because there is no way to specify an identity.
Command Name
az monitor scheduled-query create Extension Name: scheduled-query. Version: 1.0.0b1.
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Provide a query that accesses Azure Resource Graph (arg)
Expected Behavior
Command needs an additional parameter to specify the identity, which looks like it was added in version
2022-08-01-preview
of the API.https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/change-log/scheduledqueryrules#2022-08-01-preview.
Other queries I've added via the cli command appear to be created using api version
2021-08-01
Environment Summary
Additional Context
This is the option you get when creating via the portal:
![Image](https://private-user-images.githubusercontent.com/45154432/394551735-27eb2225-3283-4dc8-b0b5-d337afb8e79e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MzY3MjYsIm5iZiI6MTczODkzNjQyNiwicGF0aCI6Ii80NTE1NDQzMi8zOTQ1NTE3MzUtMjdlYjIyMjUtMzI4My00ZGM4LWIwYjUtZDMzN2FmYjhlNzllLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDEzNTM0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk5ZjQwNGNlMzYwMTkwYWRiMjMzODBkOWQzNGVjN2Q4MWJkNTk4OTE3OGEzZGE0ODEwODdhOGUyYzZjMjZkNzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZBZqUgdcL_QllTMVhPS0AQjoPr-ZfGCvLYTG6DeW4zA)
The text was updated successfully, but these errors were encountered: