-
Notifications
You must be signed in to change notification settings - Fork 250
Create version-support.md #15722
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
base: master
Are you sure you want to change the base?
Create version-support.md #15722
Conversation
As discussed in [Protecting users against stale IaC dependencies](https://docs.google.com/document/d/1nI83PEsgRVSSZyiVpMyIds4W2bCRcCVh3zmlO8_qUQI/edit?tab=t.0#heading=h.707ppz8ffokm), publishing a clear policy on which versions of providers are supported by Pulumi would help our users better manage risk (and clarify expectations for our team as well). This document attempts to clarify Pulumi's current support posture for the providers we maintain as well as offering some guidance for users on how to think about planning for upgrades.
Your site preview for commit f332dac is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-15722-f332dacb.s3-website.us-west-2.amazonaws.com. |
Your site preview for commit 106f018 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-15722-106f018a.s3-website.us-west-2.amazonaws.com. |
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.
I had one question on the line spacing. I don't think it's a showstopper, just a stylistic suggestion for maintainability. LMK if you'd like me to take a quick pass at it. 🙂
Your site preview for commit f9f4ebc is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-15722-f9f4ebc6.s3-website.us-west-2.amazonaws.com. |
As discussed in Protecting users against stale IaC dependencies, publishing a clear policy on which versions of providers are supported by Pulumi would help our users better manage risk (and clarify expectations for our team as well).
This document attempts to clarify Pulumi's current support posture for the providers we maintain as well as offering some guidance for users on how to think about planning for upgrades.
I'm not certain if the support directory is the best place for this, but it's seemed the most apt of the current options in the nav.