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

ASO V1 Deprecation #4140

Closed
AriLFrankel opened this issue Jun 27, 2024 · 2 comments
Closed

ASO V1 Deprecation #4140

AriLFrankel opened this issue Jun 27, 2024 · 2 comments
Labels
question Further information is requested

Comments

@AriLFrankel
Copy link

Howdy
I'm looking for some input on whether there are any short term plans to deprecate any APIs in use by ASO V1? As my team looks to prioritize upgrading from V1 → V2, we are trying to understand the level of urgency of this upgrade.
Thank you :)

@matthchr
Copy link
Member

Azure themselves is deprecating MySQL single server and PostgreSQL single server, so if you're using either of those two resources there is a deadline for migration. That change is outside of the ASO teams control as the whole Azure resource is being deprecated, regardless of if it's created via ASO, BICEP, Terraform, etc.

Other than that, there's nothing we're doing to force you off of ASOv1 in any particular timeframe. ASOv1 should continue to work. With that said, ASOv1 is EoL at this point and we're not updating it regularly anymore. We would definitely recommend you look into migrating from ASOv1 -> ASOv2 when you have time. We've got a document on tips for performing that migration here. If you run into any issues or gaps in that process let us know.

@matthchr matthchr added question Further information is requested and removed needs-triage 🔍 labels Jun 27, 2024
@super-harsh super-harsh added the waiting-on-user-response Waiting on more information from the original user before progressing. label Jul 1, 2024
@matthchr matthchr removed the waiting-on-user-response Waiting on more information from the original user before progressing. label Jul 15, 2024
@matthchr
Copy link
Member

Closing this as we believe the question has been answered. If not, feel free to reply here or reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Development

No branches or pull requests

3 participants