Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to configure using socket instead of URL #47

Open
yakatz opened this issue Dec 31, 2019 · 1 comment
Open

Unable to configure using socket instead of URL #47

yakatz opened this issue Dec 31, 2019 · 1 comment

Comments

@yakatz
Copy link
Contributor

yakatz commented Dec 31, 2019

I am still debugging this and I will try to submit a PR, but wanted to add a placeholder issue in case anyone has tried this and knows what is going on.
@yakatz
Copy link
Contributor Author

yakatz commented Jan 6, 2020 •
edited
Loading

Turns out this is only an issue with trying to use a Unix Domain Socket. Using TCP to connect to the agent works fine.

Changing this depends on the vault gem:
hashicorp/vault-ruby#217

To help people find this issue: Related to #33

yakatz added a commit to yakatz/petems-hiera_vault that referenced this issue Jan 6, 2020
@yakatz
Add note about using with Vault Agent
40b5007 
See petems#47
@yakatz yakatz mentioned this issue Jan 6, 2020
Merged
petems pushed a commit that referenced this issue Jan 6, 2020
@yakatz @petems
Add note about using with Vault Agent (#49)
a8cb241 
See #47
@petems petems changed the title Issues communicating through Vault Agent Unable to configure using socket instead of URL May 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yakatz