Mixing
How can we write secrets to vault without exposing them during plan/apply in logs?
I am trying to generate to generate a random string as a password for RDS and then writing this back to the vault (using vault_generic_secret resource). I am successful in doing so, but the problem is the password is shown in the output of Jenkins logs.
I think this issue is addressed in newer versions of Vault provider. But I cannot upgrade the provider version (using 1.2.0 atm) as it is managed by another team. So the options which I thought is like generating a random string using the random_string resource and writing it back to Vault using curl. In this way, I won't have to use a vault_generic_secret resource and hence no password would be revealed in Jenkins build logs.
Someone mentioned wrapping the terraform code and then tossing on a +x to it. Eg: /bin/bash +x terraform plan ..
But when I ran the following code
sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}"
It threw an error saying -
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 150: expecting '}', found 'terraform plan -no-color -out=tfplan -input=false -var-file=' @ line 150, column 11. sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}" ^
jenkins terraform jenkins-groovy hashicorp-vault terraform-provider-aws
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
add a comment |
I am trying to generate to generate a random string as a password for RDS and then writing this back to the vault (using vault_generic_secret resource). I am successful in doing so, but the problem is the password is shown in the output of Jenkins logs.
I think this issue is addressed in newer versions of Vault provider. But I cannot upgrade the provider version (using 1.2.0 atm) as it is managed by another team. So the options which I thought is like generating a random string using the random_string resource and writing it back to Vault using curl. In this way, I won't have to use a vault_generic_secret resource and hence no password would be revealed in Jenkins build logs.
Someone mentioned wrapping the terraform code and then tossing on a +x to it. Eg: /bin/bash +x terraform plan ..
But when I ran the following code
sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}"
It threw an error saying -
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 150: expecting '}', found 'terraform plan -no-color -out=tfplan -input=false -var-file=' @ line 150, column 11. sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}" ^
jenkins terraform jenkins-groovy hashicorp-vault terraform-provider-aws
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55
add a comment |
I am trying to generate to generate a random string as a password for RDS and then writing this back to the vault (using vault_generic_secret resource). I am successful in doing so, but the problem is the password is shown in the output of Jenkins logs.
I think this issue is addressed in newer versions of Vault provider. But I cannot upgrade the provider version (using 1.2.0 atm) as it is managed by another team. So the options which I thought is like generating a random string using the random_string resource and writing it back to Vault using curl. In this way, I won't have to use a vault_generic_secret resource and hence no password would be revealed in Jenkins build logs.
Someone mentioned wrapping the terraform code and then tossing on a +x to it. Eg: /bin/bash +x terraform plan ..
But when I ran the following code
sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}"
It threw an error saying -
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 150: expecting '}', found 'terraform plan -no-color -out=tfplan -input=false -var-file=' @ line 150, column 11. sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}" ^
jenkins terraform jenkins-groovy hashicorp-vault terraform-provider-aws
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
I am trying to generate to generate a random string as a password for RDS and then writing this back to the vault (using vault_generic_secret resource). I am successful in doing so, but the problem is the password is shown in the output of Jenkins logs.
I think this issue is addressed in newer versions of Vault provider. But I cannot upgrade the provider version (using 1.2.0 atm) as it is managed by another team. So the options which I thought is like generating a random string using the random_string resource and writing it back to Vault using curl. In this way, I won't have to use a vault_generic_secret resource and hence no password would be revealed in Jenkins build logs.
Someone mentioned wrapping the terraform code and then tossing on a +x to it. Eg: /bin/bash +x terraform plan ..
But when I ran the following code
sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}"
It threw an error saying -
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 150: expecting '}', found 'terraform plan -no-color -out=tfplan -input=false -var-file=' @ line 150, column 11. sh +x "terraform plan -no-color -out=tfplan -input=false -var-file=${tfvars}" ^
jenkins terraform jenkins-groovy hashicorp-vault terraform-provider-aws
jenkins terraform jenkins-groovy hashicorp-vault terraform-provider-aws
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
asked Jan 1 at 17:22
Ash PanwarAsh Panwar
356
356
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55
add a comment |
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997459%2fhow-can-we-write-secrets-to-vault-without-exposing-them-during-plan-apply-in-log%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997459%2fhow-can-we-write-secrets-to-vault-without-exposing-them-during-plan-apply-in-log%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That is a syntax error due to code that is somewhere else.
– Matt Schuchard
Jan 2 at 11:55