-
Notifications
You must be signed in to change notification settings - Fork 206
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
Bump monitor API version #4507
Bump monitor API version #4507
Conversation
d13237b
to
dc357be
Compare
@microsoft-github-policy-service agree company="UiPath" |
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! Just a few minor comments below.
v2/samples/insights/v1api/v1api20240101preview_scheduledqueryrule.yaml
Outdated
Show resolved
Hide resolved
v2/samples/insights/v1api/v1api20240101preview_scheduledqueryrule.yaml
Outdated
Show resolved
Hide resolved
771df97
to
7884677
Compare
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! Just a minor thing without which CI won't pass is that you're missing a recording for sample test. You can run TEST_FILTER=Test_Samples_CreationAndDeletion task controller:test-integration-envtest
command in root which'll test your latest sample(s) and create a recording.
Checking if you'd like this merged (or need help?) let us know! |
We're going to publish the v2.13 release of ASO very soon and it would be good to include these in that release. Do you think you can sort out the CI issues in the next couple of days (say, by Thursday this week)? |
Did you miss committing the recordings from the tests that check the samples? CI is failing with these errors:
This usually means missing recordings for the tests. If that's not it, let me know and I'll investigate further by checking out your PR locally. |
@theunrepentantgeek The tests were actually failing because of a non-retryable 400 error received when the role assignment was not ready (the samples use a managed identity). Had to add a case to the ErrorClassifier for ScheduledQueryRuns (found your PR here) and I've since committed the test recording as well. Please let me know if the classifier change needs to be a separate PR or if they can be merged together. |
Together should be fine. |
/ok-to-test sha=0125a98 |
There was a sample moved which I missed, caused a "missing recording" event. Sorry @matthchr for the back and forth on this |
I think we're getting close to a clean build. Getting a single lint error - maybe this indicates a missing assertion?
|
/ok-to-test sha=7e5ed65 |
/ok-to-test sha=62123ec |
What this PR does
Update the version of the
Microsoft.Insights/scheduledQueryRules
to catch up with https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/change-log/scheduledqueryrules#2024-01-01-previewThe new version comes with some features, including the addition of a
.spec.identity
field which allows using an existing user assignment identity when the service executes the query. This was captured in a focused test, which creates the necessary prerequisites before instantiating the object.How does this PR make you feel?
Checklist