You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create main.tf with the content above, maybe adjust the provider configuration
Run terraform plan
Debug Output
No response
Panic Output
No response
Important Factoids
No, nothing special. I just wanted to add some default scopes to the default OIDC provider, but cannot import it.
As a workaround, I created an additional provider and use that.
#2227 has this labeled as documentation issue, however #1548 fixes this for scope. I have a local version I fiddled with based on the scope one that got provider and client working I can make a PR for. However, key handles the path differently.
The documentation still would need to be changed, they only work with the path (not the name as the documentation for all of them state), i.e. identity/oidc/client/whatever, but key simply takes the name (I could add that to the PR?) unless more significant changes are made that I'd need more time with before I felt ok submitting it.
Terraform Core Version
1.9.2
Terraform Vault Provider Version
3.23.0, 4.3.0
Vault Server Version
1.17.0
Affected Resource(s)
Expected Behavior
An import should work (see https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/identity_oidc_provider#import).
Actual Behavior
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: resource vault_identity_oidc_provider doesn't support import
│
│
╵
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform plan
Debug Output
No response
Panic Output
No response
Important Factoids
No, nothing special. I just wanted to add some default scopes to the default OIDC provider, but cannot import it.
As a workaround, I created an additional provider and use that.
References
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: