-
Notifications
You must be signed in to change notification settings - Fork 5
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
Upgrade terraform provider vault to v4.2.0 #466
Upgrade terraform provider vault to v4.2.0 #466
Conversation
Does the PR have any schema changes?Does the PR have any schema changes?Found 3 breaking changes: Resources
New functions:
Maintainer note: consult the runbook for dealing with any breaking changes. |
Is README.md missing any configuration options?
Please add a description for each of these options to |
@iwahbe not sure what to do here, would appreciate some help resolving this upgrade. |
"auto-settings": { | ||
"datasources": { | ||
"vault_namespace": { | ||
"renames": [ | ||
"vault:namespace/get:get" | ||
] | ||
}, | ||
"vault_namespaces": { | ||
"renames": [ | ||
"vault:namespace/getS:getS" | ||
] | ||
} | ||
} | ||
}, | ||
"renames": { |
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.
Are these renames the issue?
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.
Probably. I regenerated everything after resetting bridge-metadata.json
and SDKs seemed to build.
tries to address #458
the
build_sdks
step is failing with:Looks like the Namespace resource is conflicting with the namespace module?
pulumi-vault/provider/resources.go
Line 206 in 2cc7d4b