apogrebnyak

Will it support a `*` for any workspace, so we can have selective controls through labels only?

For declarative pipeline, initialize AWS credentials in the environment block. It is pretty concise, ``` stage("my aws stage") { environment { NOOP_CREDS_VAR = credentials('my-example-creds') } steps { sh 'env' sh...

The issue arises with using `terraform_iam_policy` in outputs of calling code. Also, just verified that the problem still exists in 0.4.0 version Here is the one-pager that demonstrates the problem...

> I'm using TF 0.13.4 and also can't reproduce, even when outputting `module.remote_state.terraform_iam_policy.arn`. > From your code, I wonder if your issue is that the replica is in the same...

> Two providers must point to different AWS regions. What is the issue with pointing to the same region? I think requiring a replica in a different region is an...

For AWS cli > 2.13.5 which uses sso-session sections in configuration file, you need to change the SHA1 source to `sso_session` value in your profile ```bash ... local sso_session="$(aws configure...

Here is a workaround to get to the JSON cache file until this issue is fixed: For AWS cli > 2.13.5 the name of the cache file is the sha1sum...

May be related to https://github.com/warrensbox/terraform-switcher/issues/303 Note, that if it cannot install to `/usr/local/bin/terraform` it falls back to installing to `~/bin/terraform` Make sure that your `~/bin` directory is on your PATH....

For me specifying the S3 endpoint URL in the correct region worked. ``` export AWS_ENDPOINT_URL_S3="https://s3.us-west-2.amazonaws.com" aws cloudformation deploy --region ap-south-1 --s3-bucket my-bucket-in-us-west-2 ... ``` If you don't want to fix...