-
Notifications
You must be signed in to change notification settings - Fork 1
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
Allow missing docs when upgrading bridged providers #303
Labels
Comments
This was referenced Feb 3, 2025
VenelinMartinov
added a commit
to pulumi/pulumi-upgrade-provider-action
that referenced
this issue
Feb 4, 2025
This will allow us to opt-in Tier 1 providers and opt-out all the rest Related to pulumi/upgrade-provider#303
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this issue
Feb 4, 2025
This config will allow us to opt-out Tier 1 providers and opt-in Tier2+ providers. Currently defaults to False, will flip to True once we opt-out Tier 1 providers. Related to pulumi/upgrade-provider#303
This was referenced Feb 11, 2025
VenelinMartinov
added a commit
to pulumi/pulumi-azure
that referenced
this issue
Feb 11, 2025
Sets the `allowMissingDocs` ci-mgmt config to false to error on missing resource docs. This maintains the current behaviour. Part of pulumi/upgrade-provider#303
VenelinMartinov
added a commit
to pulumi/pulumi-azuread
that referenced
this issue
Feb 11, 2025
Sets the `allowMissingDocs` ci-mgmt config to false to error on missing resource docs. This maintains the current behaviour. Part of pulumi/upgrade-provider#303
VenelinMartinov
added a commit
to pulumi/pulumi-azure
that referenced
this issue
Feb 11, 2025
Standing this up again as I accidentally merged #3003 into the other branch. Sets the `allowMissingDocs` ci-mgmt config to false to error on missing resource docs. This maintains the current behaviour. Part of pulumi/upgrade-provider#303
VenelinMartinov
added a commit
to pulumi/pulumi-gcp
that referenced
this issue
Feb 11, 2025
Sets the `allowMissingDocs` ci-mgmt config to false to error on missing resource docs. This maintains the current behaviour. Part of pulumi/upgrade-provider#303
VenelinMartinov
added a commit
to pulumi/pulumi-aws
that referenced
this issue
Feb 11, 2025
Sets the `allowMissingDocs` ci-mgmt config to false to error on missing resource docs. This maintains the current behaviour. Part of pulumi/upgrade-provider#303
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this issue
Feb 11, 2025
This PR changes all Tier2+ providers to allow missing resource docs when running a provider upgrade. This is a common issue which happens and we have to manually work around. Fixes pulumi/upgrade-provider#303 Tier 1 providers are exempt as the config is explicitly false there: pulumi/pulumi-gcp#2971 pulumi/pulumi-aws#5193 pulumi/pulumi-azure#3003 pulumi/pulumi-azuread#1877
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this issue
Feb 12, 2025
This PR changes all Tier2+ providers to allow missing resource docs when running a provider upgrade. This is a common issue which happens and we have to manually work around. Fixes pulumi/upgrade-provider#303 Tier 1 providers are exempt as the config is explicitly false there: pulumi/pulumi-gcp#2971 pulumi/pulumi-aws#5193 pulumi/pulumi-azure#3003 pulumi/pulumi-azuread#1877
github-merge-queue bot
pushed a commit
to pulumi/ci-mgmt
that referenced
this issue
Feb 19, 2025
Thomas spotted some warnings related to some recent changes to upgrade-provider-action: https://github.com/pulumi/pulumi-azuredevops/actions/runs/13382459741/job/37373285196 Looks like we never bumped the version of the action so the `allow-missing-docs` arg was not recognized. Related to #1379 Related to pulumi/upgrade-provider#303
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Upstream provider upgrades for bridged providers often fail due to missing documentation upstream from new resources. We should allow this instead of having to manually work around it each time.
Longer discussion: https://docs.google.com/document/d/1MTMSceicK9hrnnIuJ2OyhOktcgIc7EBNENyRFStG27s/edit?tab=t.0
The text was updated successfully, but these errors were encountered: