Roxyrob

I apologize but I didn't try from start as documentation says `This option is deprecated`. **Effectively it seems to work.** Why the documentation tells about **deprecation** ? Note some possible...

For issue part (1.) as **workaround** casting to bool seems to work: update: {{(myupdate|default(omit))|bool}}

Thank you @TerryHowe for your response and for the work for these ansible/hashicorp vault integration modules. AWS secret engine need a secret engine backend definition (of type aws) like this:...

Terraform deployment environment protection using separated Cloud Providers accounts is a great method to reduce configuration/deployment error Blast Radius. E.g. different AWS accounts can be used to make deployment environments...

YAML tags are not a language standard ?

I've got it. Thanks

This is an important use case to really rise AWS security and achieve "**Zero AWS IAM Static Credentials**" (removing risk on AWS IAM credentials management) and so reaching a **Zero...

I think one solution would be to use **AWS Secret Engine "iam_user"** to get **AWS IAM User** access/secret keys and request a **federated token** ([**GetFederationToken**](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetFederationToken.html)). With GetFederationToken response Vault can...

(**Checked**) Vault AWS Secret Engine type "**federation_token**" return federation token (as the name implies...). To get a **Login URL** it is needed to get **Sign-in Token** ([login.go => sample code...

Hi @gavinelder voted same issue #26742 thanks