Skip to content
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

Retirement of API versions 2022-06-01-preview and 2022-11-01-preview? #876

Closed
1 of 3 tasks
YuKogasaka opened this issue Aug 17, 2023 · 2 comments
Closed
1 of 3 tasks
Labels
Needs: triage 🔍 Pending a first pass to read, tag, and assign

Comments

@YuKogasaka
Copy link

YuKogasaka commented Aug 17, 2023

This issue is a: (mark with an x)

  • bug report -> please search issues before submitting
  • documentation issue or request
  • regression (a behavior that used to work and stopped in a new release)

Issue description

I received an email titled "Action required: Retirement of Azure Container Apps versions" in only one of my multiple subscriptions running Azure Container App (ACA).
// See the screenshot for the content of the email.

I checked the contents of the email, but there is no difference from ACA running in other subscriptions, so I don't know how to respond.

I have two questions:

  • Conditions for receiving this email
  • Any action that needs to be taken (e.g. Azure CLI update or SDK update in incoming code deploying ACA)

Steps to reproduce

Nothing in particular (an email from Microsoft Azure arrives)

ScreenShots
20230817-01

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Aug 17, 2023
@anthonychu
Copy link
Member

This was sent to subscriptions who our logs show had recently made management API calls using the retiring API versions. What do you use to manage your container apps (portal, CLI, Bicep, etc)?

@YuKogasaka
Copy link
Author

@anthonychu,

I understand the conditions for receiving "Action required" emails.

Different units within a project use different tools to manage ACA.

  • Develop unit : Bicep
  • Operations unit : Azure CLI and Azure Portal

I recognize that this issue occurred because the unit and members were not properly updated and specified for each tool (API version).

This issue has been resolved, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: triage 🔍 Pending a first pass to read, tag, and assign
Projects
None yet
Development

No branches or pull requests

2 participants