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.
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
[Container Registry] Migrate to new recorder #20301
[Container Registry] Migrate to new recorder #20301
Changes from 5 commits
2510424
a4f6a63
95c540d
4f11c49
4cff5f0
cac8977
ea35749
d09107c
863f25f
0a09d76
644f623
e61212b
43f515a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
When I created the weekly live test pipeline,
AZURE_*_*
env vars didn't work for other clouds because they were set to the Public cloud's client/tenant. It is likely to be fixed now. Please trigger thejs - container-registry - tests-weekly
pipeline to make sure it's working. https://dev.azure.com/azure-sdk/internal/_build?definitionId=2886There 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.
I'll trigger that soon. I changed these back to their usual names so that the
createTestCredential
helper could be used -- it uses the standard names when creating the credential. If the issue still exists, then I can revert to using theCONTAINERREGISTRY_*
names and switch betweenNoOpCredential
and theDefaultAzureCredential
without the helper.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.
I didn't know this.
Maybe update the test-credential package to take more options?
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.
Appears to be failing, I'll add an option to test-credential.
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.
We may want to fix the pipeline instead? I thought it is expected that
Azure_*
is set to be the ones from the cloud being tests against. @benbpThere 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.
Not blocking this PR. But I'd love to not special case ACR.
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.
The change to add options to the test credential is nice to have anyway IMO regardless of whether we fix the underlying issue here.
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.
We have not historically set
AZURE_*
variables and instead set namespaced variables likeCONTAINERREGISTRY_*
in the test infastructure to avoid potential collisions when running test batches. I have an issue to fix this though, as in practice it hasn't been an issue. A current workaround is to set a redirect in the pipeline definition, e.g. here.Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.