Written by Jamie Tanna
on June 15, 2020
CC-BY-NC-SA-4.0 Apache-2.0
1 mins

Issues with Ordering When Using Vault CLI's `-no-print` Argument

Today I've been fighting a bit of an issue with the Vault CLI (v1.1.2) not masking the output of a vault login.

It appears that this is due to the ordering of the arguments I was using:

-vault login -method=aws -path=aws-ec2 role=.... -no-print=true
+vault login -no-print=true -method=aws -path=aws-ec2 role=....

In the former command, it appears that the EC2 auth takes arguments (i.e. role) which are slightly different to Vault's usual arguments, such as -no-print.

By moving it earlier in the command, it no longer prints output for the result of login.

Written by Jamie Tanna on Mon, 15 Jun 2020 10:59:02 +0100, and last updated on Mon, 15 Jun 2020 10:59:02 +0100.

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #vault #aws.

This post was filed under articles.

Has this content helped you? Please consider supporting me so I can continue to create content like this!

Issues with Ordering When Using Vault CLI's -no-print Argument

Interactions with this post

Issues with Ordering When Using Vault CLI's `-no-print` Argument