Dimitris Moraitidis

This would be super nice to have, in light of Dependabot's support for version updates for private terraform registries: - https://github.com/dependabot/dependabot-core/tree/main/terraform - https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#terraform-registry

This can be achieved via `dig +short A`. It's a DNS thing, not really HTTP

Any news regarding this?

bump

Hi @ScottGuymer , yeah, one idea would be to install a cron inside the runners that checks regularly for spot interruption notices (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-instance-termination-notices.html), then it would deregister itself from...

This did the trick for me: assuming a clean npm installation ``` sudo mkdir -p /usr/local/lib/node_modules && sudo chown -R $(whoami):$(whoami) /usr/local/lib/node_modules npm install -g terminalizer ``` Then you should...

Documented successful run of this in: https://github.com/dtan4/terraforming/issues/356 Let's merge!

@ddreggors @cmedley Using both `--assume` and `--profile` still doesn't work for me. I am getting: ``` /var/lib/gems/2.5.0/gems/aws-sigv4-1.1.0/lib/aws-sigv4/signer.rb:670:in `credentials_set?': undefined method `access_key_id' for nil:NilClass (NoMethodError) ``` My ~/.aws/credentials looks like this:...

@cmedley `terraforming s3 --region=eu-west-1 --assume=arn:aws:iam:::role/ --profile=` Getting the same if I put `--profile` arg before `--assume` or if I have exported `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_REGION` or not

@cmedley Awesome! How can I test this?