-
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
Containerapp Version 0.3.7 #4960
Conversation
`az containerapp env create`: Fix bug with `--internal-only`
Containerapp |
`az containerapp registry set`: remove username/password if setting identity and vice versa
…128) * Fixed issue where containerapp up would not honor --registry-server. * Updated history. Co-authored-by: Haroon Feisal <haroonfeisal@microsoft.com>
Could you add some tests for those change? |
@zhoxing-ms just added some tests |
@AllowLargeResponse(8192) | ||
@ResourceGroupPreparer(location="northeurope") | ||
@live_only() # passes live but hits CannotOverwriteExistingCassetteException when run from recording |
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.
passes live but hits CannotOverwriteExistingCassetteException when run from recording
What is the specific information of this exception? Can't you pass the test in record mode even locally?
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.
No, the test does not pass when run from a recording locally -- despite passing in live mode. Here's the terminal output for the related CannotOverwriteExistingCassetteException
Given that we've got multiple users asking for the bug fixes in this release, could we go ahead and merge this and circle back to the live_only issues later?
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.
OK, sounds good
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.json
automatically.The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify
src/index.json
.