Commit b2fdbcb4 authored by Jamie Tanna's avatar Jamie Tanna

Blogument Vault CLI ordering issue

Closes #982.
parent ad22faf4
Pipeline #156260604 passed with stages
in 13 minutes and 11 seconds
title: "Issues with Ordering When Using Vault CLI's `-no-print` Argument"
description: "A possible solution for `no-print` not taking effect with the `vault` CLI when using AWS EC2 auth."
- blogumentation
- vault
- aws
license_code: Apache-2.0
license_prose: CC-BY-NC-SA-4.0
date: 2020-06-15T10:59:02+0100
slug: "vault-no-print-ordering"
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`.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment