-
Notifications
You must be signed in to change notification settings - Fork 540
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
Error using vault_generic_endpoint
to register a custom plugin
#1975
Comments
vault_generic_endpoint
to register a custom plugin
Thanks for the report. What are the input variables please? The API accepts tags with or without a leading 'v', but normalises to including the leading 'v', so I wonder if that might be causing the issue here. |
Config looks like the below, so no leading config = {
tag = "8588d498fb0e241dccf92b59dc5732b116906de2"
sha256 = "f5801170e8a3575268e32bfdce9c7a1c323ffc610793da8ead14680fd0596e68"
version = "0.1.2"
} |
If it is helpful, this happens when using |
@anthonyralston Hello! Can you confirm that the plugin failed to register? When I use the config you provided I am able to register the plugin successfully despite receiving the error from the provider. You can check with:
I think the error is occurring because the GET plugin endpoint requires the version if the plugin was registered with a version. In that case you may want to set disable_read and disable_delete in vault_generic_endpoint
|
@anthonyralston Hello! Is there any recent update on this issue? Are you still experiencing this issue? |
Terraform Version
v1.3.2
Affected Resource(s)
vault_generic_endpoint
to pathsys/plugins/catalog/secret/some-custom-plugin
Terraform Configuration Files
Expected Behavior
Apply is successful.
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
The text was updated successfully, but these errors were encountered: