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.

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

Clarification required about vault_checksum_file_url variable content for Enterprise Install #89

Open
planetrobbie opened this issue Apr 9, 2019 · 1 comment

Comments

@planetrobbie
Copy link
Contributor

While deploying an Enterprise Vault/Consul Cluster for a customer, I discovered the following issue.

While setting up vault_checksum_file_url to the location where to find the Enterprise checksum for Vault Enterprise binary, which by default is set to https://releases.hashicorp.com/vault/{{ vault_version }}/vault_{{ vault_version}}_SHA256SUMS for OSS which is the file itself. I encountered a failure scenario because in install_enterprise.yml Ansible add at the end of this URL another {{ vault_enterprise_shasums }} value.

So I ended up having something like this, which is obviously failing :/

https://FQDN/.../vault/ent/1.1.0/vault-enterprise_1.1.0%2Bent_SHA256SUMS/vault-enterprise_1.1.0%2Bent_SHA256SUMS

So I presume we should better document what is expected in that variable, I mean not the location of the SHASUM but the first part of the URL, or update Ansible code to align with the way it works for Open Source. Just my 2 cents.

Hope that helps.

@planetrobbie planetrobbie changed the title Clarification required about vault_checksum_file_url for Enterprise Install Clarification required about vault_checksum_file_url variable content for Enterprise Install Apr 9, 2019
@brianshumate
Copy link
Contributor

Thanks for reporting this!

Sorry that you've had trouble with it, but I'll try to fix up the documentation to better describe what's going on wit that variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants