-
Notifications
You must be signed in to change notification settings - Fork 356
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
[Feature Request]: Add a Variable Resolver for Hashicorp Vault #4771
Labels
Comments
See also: issue #3454 |
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 10, 2025
Improvements for issue apache#3454 (option to disable variable resolving in tooltips)
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 10, 2025
Improvements for issue apache#3454 and documentation
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 14, 2025
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 14, 2025
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 14, 2025
mattcasters
added a commit
to mattcasters/hop
that referenced
this issue
Jan 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to happen?
I would love to have a way to resolve variables directly against a Hashicorp Vault server.
It should allow me to enter a path and a value to look up, for example:
#{vault:dwh/some-db:hostname}
should resolve to some hostname.We should always resolve to the String representation of the value in the secret.
Issue Priority
Priority: 3
Issue Component
Component: Other
The text was updated successfully, but these errors were encountered: