-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[ACR] az acr connected-registry: Add --notifications argument to support the list of artifact pattern for which notifications need to be generated
#20763
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
Conversation
Add notifications list to acr connected-registry create and update commands
|
@zhoxing-ms Can you please help me with this? I don't understand the reason for build failure. I created live recording and pushed them. However I am noticing the failures |
src/azure-cli/azure/cli/command_modules/acr/connected_registry.py
Outdated
Show resolved
Hide resolved
src/azure-cli/azure/cli/command_modules/acr/connected_registry.py
Outdated
Show resolved
Hide resolved
src/azure-cli/azure/cli/command_modules/acr/linter_exclusions.yml
Outdated
Show resolved
Hide resolved
az acr connected-registry: Add --notifications-list argument
az acr connected-registry: Add --notifications-list argumentaz acr connected-registry: Add --notifications-list argument to support the list of artifact pattern for which notifications need to be generated
src/azure-cli/azure/cli/command_modules/acr/connected_registry.py
Outdated
Show resolved
Hide resolved
|
ACR |
|
@savaradh Any update? Please note that we will launch the release of this sprint the day after tomorrow. If you can't address these comments tomorrow, this PR will not catch up with the release of this sprint and can only be postponed to the next sprint (02-08) |
|
@zhoxing-ms Thank you. I will fix the tests and push it today. I would like to get it on today's release |
az acr connected-registry: Add --notifications-list argument to support the list of artifact pattern for which notifications need to be generatedaz acr connected-registry: Add --notifications argument to support the list of artifact pattern for which notifications need to be generated
|
@savaradh Sorry, because the comments were resolved a little late, and included upgrading api-version, this poses a risk to the quality of CLI and may blocking CLI release. |
Please re-run the |
|
@zhoxing-ms no problem. The PR was delayed cause of the holidays. Please keep me posted if there is any change in the release dates. I am still trying to fix one test which I am unable to record in live mode. It is skipped when I run locally and I reached out to my team to help fix it. We can merge the PR once I fix it. |
|
The test is skipped when I try to run on live mode. I notice the annotation @record_only() for that particular test. |
|
Yes, the tests annotated with |
|
Thank you for the details @zhoxing-ms . I manually updated the api version on the recording. |
|
@jsntcy @kairu-ms @wangzelin007 Can one of you review this change so that I can get it merged? Thanks |
|
@zhoxing-ms Can you please merge this? |
|
LGTM |
|
@zhoxing-ms Can you please merge this? The history notes has been approved |
Description
Add notifications list to acr connected-registry create and update commands
History Notes
[ACR]
az acr connected-registry create: Add--notificationsto support adding patterns for generating notification events on connected registry artifacts[ACR]
az acr connected-registry update: Add--add-notificationsand--remove-notificationsto support adding or removing patterns for generating notification events on connected registry artifactsThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.