[Epic] Azure Native v3 release

[mjeffryes]

Overview

It's been roughly a year since we last released Azure native. We want to release a new major version (v3), in order to:

1. bumping all the default API versions to the latest reasonable one (details) (consolidating and shrinking the SDK bloat since v2), and
2. implementing fixes and improvements that are breaking changes.

Key KPIs

1. 0 regressions introduced by this release
2. SDK size should be in the ballpark of v2.0.0
3. Closes ~80% of the issues labeled 3.0, i.e., ~17 issues, including all blocking ones
4. Adoption: 100% of net-new azure-native users start on v3 after GA
5. Adoption: TODO% of existing users upgrade to v3 within three months

Key Stakeholders

Engineers: @danielrbradley and @thomas11

Approvers: @mjeffryes

@pulumi/docs to coordinate and help with docs updates

Marketing for promotion

Key Deliverables

• V2 -> V3 release notes with breaking changes and upgrade instructions
• Official release of V3
• pulumi/examples are updated to v3
• pulumi/templates are updated to v3
• Blog post
• Registry docs for V2 are preserved for some amount of time

References 📔

• Project View
• PR/FAQ
• Design Doc
• Decision Log

Basic Process

1. Start implementing the non-breaking issues that can go into master, especially those that influence the automatic part of the major version upgrade
   • Use the Azure RP API when determining default API versions
   • Do not squeeze API versions of resources when the path differs
2. Create v3 branch
3. In parallel
   • Choose new API versions
     • Run discovery to bump default versions
     • Run schema squeeze to remove older versions which can be safely upgraded.
     • Manually curate version selection
   • Implement epic/project issues

[mjeffryes]

closing in favor of https://github.com/pulumi/home/issues/3552

[pulumi-bot]

Cannot close issue:

• does not have required labels: resolution/

Please fix these problems and try again.

[1oglop1]

@mjeffryes the linked issue is 404 (perhaps it is a private project). Is there any public information about this? Eventually you could unpin the issue to prevent the confusion.
Thank you!

[mjeffryes]

I apologize for the inconvenience @1oglop1! I missed that the new issue was private; we'll flip it around and close that one as the duplicate and work here instead.

[cleverguy25]

[Project] Azure Native V3 status update
Work on the epic has started for real, with Eron helping out the Azure squad. I (tkappler) haven't actually been participating yet due to customer issues and Insights but hope to join soon.

Two must-have and three should-have items have already landed and work on others is in progress.

No blockers have been encountered so far.

View all status updates

[pulumi-bot]

[Project] Azure Native V3 status update
What we did this week:

• Finished customised module naming approach to let us start splitting up problematic modules.
• Finished skipping flattening if it causes a clash.
• Nearly finished disambiuating resource naming for incompatible paths.
• Created initial v3 version selection which creates a valid schema.

What we'll do next week

• Finish upgrade tests so we can validate migrations to the new schema.
• Merge path disambiguation.
• Fix aliases for upstream resource case changes.

Next milestone/deliverable

• Prepare documentation, examples & templates.
• Alpha release for testing.

View all status updates

[pulumi-bot]

[Project] Azure Native V3 status update
What we did this week:

• Got first big round of upgrade tests in place
• Got the v3 branch fully generated and passing existing tests
• Made good progress on resolving path conflicts

What we'll do next week

• Finish path conflict resolution
• Alias based on matching paths from v2 default resources
• Hopefully cut a first alpha release

Next milestone/deliverable

• Prepare documentation, examples & templates.
• Alpha release for testing.

View all status updates

[pulumi-bot]

[Project] Azure Native V3 status update

What we got done this week

Over the last few weeks, we went back to the drawing board and discussed the provider's design and major problems with Meagan and Joe. We came to the conclusion to delay the v3 release and make the major change of dropping explicit API versions.

Since then, we've investigated a number of questions around this in more detail:

• how to determine the, now only, API version
• how users can be confident in provider upgrades
• how users can pin API versions when required

What we’ll do next week

This week (since it's Monday) we plan to have concrete proposals with a discussion of trade-offs for the above questions. We will also start implementing the new plan.

Upcoming deliverable

We hope to have a testable, if incomplete, alpha release.

View all status updates