-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Containerapp 0.3.13 Release #5426
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 0.3.13 Release #5426
Conversation
* initial no dockerfile support for up * bump version * add to help text, history text * Fill in Cormac's link for oryx runtimes (see here microsoft/Oryx#1502) * pass target port to ACR task; add better error information * bump version * fix bug with containerapp create * add test case * bump version * Updated to preview api version and reran all tests. (Azure#147) * Ran tests. * Update src/containerapp/azext_containerapp/_clients.py Co-authored-by: Silas Strawn <[email protected]> Co-authored-by: Haroon Feisal <[email protected]> Co-authored-by: Silas Strawn <[email protected]> * resolve anthony's comments * Revert "`az containerapp up`: Support No Dockerfile Scenario" * Revert "Revert "`az containerapp up`: Support No Dockerfile Scenario"" * Added custom domain support to env create. * Updated param help group text. * Added test. * Wrote env update, wrote test for env update with custom domains. * Minor update. * Added help to env update. Co-authored-by: Silas Strawn <[email protected]> Co-authored-by: Haroon Feisal <[email protected]>
Add azure monitor support
…ceCLI/azure-cli-extensions into containerapp-0.3.13-ignite
|
Containerapp |
| @AllowLargeResponse(8192) | ||
| @ResourceGroupPreparer(location="australiaeast") | ||
| @StorageAccountPreparer(location="australiaeast") | ||
| @live_only() # encounters 'CannotOverwriteExistingCassetteException' only when run from recording (passes when run live) |
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.
May I ask what is the reason for this problem 'CannotOverwriteExistingCassetteException' only 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.
If I recall correctly, this test actually passes locally (when run from a recording or live), but fails when run in the CI. Let me try rerecording again to see if it works
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.
Yes, I just double-checked this with a rerecorded test. The test passes locally, but fails the CI for some reason. I think the best thing to do here is mark it as live_only and investigate further when we have time
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, please remember to submit PR separately to solve the @live_only() problem in the future. It is recommended that you create a work item for these testing problems
@StrawnSC This is caused by the inconsistent api-version of |
|
[Release] Update index.json for extension [ containerapp ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=7799&view=results |
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 azdevrequired)python scripts/ci/test_index.py -qlocally?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.jsonautomatically.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.