Skip to content

Commit

Permalink
Remove pulumi-vault from regular upgrade maintenance (#602)
Browse files Browse the repository at this point in the history
Due to pulumi/pulumi-vault#197, pulumi-vault
cannot currently benefit from automation per this repository. Putting it
in a separate folder to await the resolution of the blocking issue and
avoid noise and spurious p1s caused by attempts to upgrade the bridge.

Upstream upgrades will continue to run automatically as per current
state of pulumi-vault's Workflow files.

Resolution for pulumi/pulumi-vault#310.
  • Loading branch information
guineveresaenger authored Sep 21, 2023
1 parent b2d9a1d commit 0102829
Show file tree
Hide file tree
Showing 21 changed files with 14 additions and 0 deletions.
7 changes: 7 additions & 0 deletions provider-ci/blocked-providers/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Blocked Providers

This is a folder where we store provider configs that for some reason cannot currently be maintained via this
repository's automation.

In order to live in this folder, a provider folder must have a clear explanation of why it is blocked from regular
upgrades, including a link to the blocking issue.
7 changes: 7 additions & 0 deletions provider-ci/blocked-providers/vault/BLOCKED_REASON.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# pulumi-vault

This provider is blocked from bridge upgrades due to
[conflicting upstream dependencies](https://github.com/pulumi/pulumi-vault/issues/197#issuecomment-1728416238)
on `azcore.`


File renamed without changes.
File renamed without changes.

0 comments on commit 0102829

Please sign in to comment.