Skip to content

[containerapp] Fix containerapp update using yml file #31508

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

mbarton
Copy link

@mbarton mbarton commented May 19, 2025

Related command

  • az containerapp update (passing --yaml)

Description

I think the upgrade to the new API version (#31276) lead to runningStatus appearing as a field at the top level when the YAML file passed to az containerapp update is run through the deserialiser.

It then caused an error before the command was run:

(InvalidRequestContent) The request content was invalid and could not be deserialized: 'Could not find member 'runningStatus' on object of type 'ResourceDefinition'. Path 'runningStatus', line 1, position 224.'.

The fix is to add it to the existing list of readonly attributes to remove.

Testing Guide

  1. Save your current container apps template with az containerapps show --output yaml > /tmp/template.yml
  2. Try to apply it with az containerapps update --yaml /tmp/template.yml

Example Python script here: https://github.com/rcpch/national-paediatric-diabetes-audit/blob/live/s/deploy-revision.py

History Notes

[Container App] az containerapp update Modify --yaml template handling to fix runningStatus error


This checklist is used to make sure that common guidelines for a pull request are followed.

I think the upgrade to the new API version (Azure#31276) lead to `runningStatus` appearing as a field at the top level when the YAML file passed to `az containerapp update` is run through the deserialiser.

It then caused an error before the command was run:

```
(InvalidRequestContent) The request content was invalid and could not be deserialized: 'Could not find member 'runningStatus' on object of type 'ResourceDefinition'. Path 'runningStatus', line 1, position 224.'.
```

The fix is to add it to the existing list of readonly attributes to remove.
Copy link

Validation for Azure CLI Full Test Starting...

Thanks for your contribution!

Copy link

Hi @mbarton,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

Copy link

Validation for Breaking Change Starting...

Thanks for your contribution!

@yonzhan
Copy link
Collaborator

yonzhan commented May 19, 2025

Thank you for your contribution! We will review the pull request and get back to you soon.

Copy link

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

Copy link
Contributor

Thank you for your contribution @mbarton! We will review the pull request and get back to you soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot ContainerApp customer-reported Issues that are reported by GitHub users external to the Azure organization.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants