tbrb · HackerTrans

anno scorsodiscuss

The AWS SDK supports supplying credentials based on environment variables. When on my workstation I set AWS_PROFILE to select what profile I'm using, prior to running Terraform. This is then portable to CI where we may be using something like https://github.com/aws-actions/configure-aws-credentials to assume a role rather than using a pre-configured CLI profile.

tbrb

anno scorsodiscuss

I generally consider the AWS CLI configuration to be something that's unique to a developer's workstation, and shouldn't be referenced in terraform code (in the form of tying the workspace name to your AWS profile name).

This would only work if all developers on a team have synchronised the same AWS CLI config (which to me is like asking people to synchronise dotfiles, not something I'd be willing to do).

My go-to architecture for multi-environment tends to be this, as it lends itself relatively well to Git Flow (or GitHub Flow): https://github.com/antonbabenko/terraform-best-practices/tre...

tbrb

2 anni fadiscuss

The biggest life changer to me back when I worked with Mikrotik gear was learning that the '?' character was an immediate "Show me all of the commands I can get to from the current prompt", and then appending '?' to existing commands would show all of the sub commands available etc.

From that point I found the CLI to be relatively discoverable as a way to configure the devices.

tbrb

2 anni fadiscuss

Agree that it would be nice to specify credentials a different way - however as a workaround: some bash-based shells support prefixing the command with a space as a way of not saving that command into history.

Ref: https://www.gnu.org/software/bash/manual/html_node/Bash-Vari...

comments