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

Updated Ks Openshift Readme #95

Merged
merged 2 commits into from
Apr 19, 2019
Merged

Updated Ks Openshift Readme #95

merged 2 commits into from
Apr 19, 2019

Conversation

amcbarnett
Copy link
Contributor

Changed to new command vault write aws-tf/roles/deploy policy_document=-<<EOF

Changed to new command vault write aws-tf/roles/deploy policy_document=-<<EOF
@hashicorp-cla
Copy link

hashicorp-cla commented Mar 18, 2019

CLA assistant check
All committers have signed the CLA.

Added version = "~> 2.0"
@rberlind
Copy link
Contributor

Hi @amcbarnett:
Thanks for noticing the missing "" in the README.md for the vault write aws-tf/config/root command.

Regarding the change from policy to policy_document in the vault write aws-tf/roles/deploy command, I know that policy used to work and wonder if this reflects a change to a newer version of Vault. I do now see policy_document in https://www.vaultproject.io/docs/secrets/aws/index.html#setup and https://www.vaultproject.io/api/secret/aws/index.html#create-update-role but am also sure that policy used to work. Unfortunately, we don't version our docs. What version of Vault were you using?

Can I ask why you are requiring the AWS provider to be version ~2.0? Was the demo not working with older versions of the AWS provider? It should be. I don't necessarily like the idea of forcing people to use a newer version unless it is actually necessary.

@rberlind
Copy link
Contributor

I researched and found that policy was deprecated in August, 2018 in favor of policy_document. So, that is a good change in the readme.md.

I'm not convinced that we need to force AWS provider to be 2.0

Copy link
Contributor

@rberlind rberlind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amcbarnett : I'm approving this despite my reservation about forcing use of newer AWS provider. I thought I had added in the doc changes, but see I missed the \ in the vault command.

@rberlind rberlind merged commit 7159be1 into hashicorp:master Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants