Readit News logoReadit News
tbrb commented on Using Terraform Workspace for AWS multi account architectures   github.com/maurobaraldi/t... · Posted by u/maurobaraldi
thayne · a year ago
So how do you manage getting credentials for different accounts?
tbrb · a year ago
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 commented on Using Terraform Workspace for AWS multi account architectures   github.com/maurobaraldi/t... · Posted by u/maurobaraldi
tbrb · a year ago
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 commented on US could ban TP-Link routers over hacking fears: report   nypost.com/2024/12/18/bus... · Posted by u/esaym
ssl-3 · a year ago
Mikrotik gear absolutely runs Linux. It just uses a custom userland.

Ubiquity gear is structured the same way: It, too, absolutely runs Linux, and it uses a custom userland.

One of these userlands is friendlier than the other, but they're both still Linux.

It's a tale as old as the hills, or at least as old as the OG Linksys WRT54G -- which was my own first foray into owning dedicated routing hardware ~20 years ago (which was -- guess what -- Linux with a custom userland). (Previous to that, I used Linux with the userland of my choosing on my desktop PC.)

tbrb · a year ago
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 commented on Rainfrog – a database management TUI for Postgres   github.com/achristmascarl... · Posted by u/achristmascarl
askvictor · a year ago
Looking forward to trying it, though would be nice if credentials could be specified in a different way than on the command line (whereby they'll get saved into your command line history).
tbrb · a year ago
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...

tbrb commented on Show HN: Relay – Event-driven DevOps automation   relay.sh... · Posted by u/product1087
bradhe · 6 years ago
Hey there, as mentioned elsewhere I'm an engineer on Relay. Our PM is busy right now so thought I'd jump in.

> Have you any comparisons between this and StackStorm?

Relay is very similar to StackStorm! One of the biggest differences between Relay and StackStorm, however, is that every step and trigger in Relay is just a docker container. You can basically run any container you want, but containers that are authored specifically for Relay are, obviously, better (integration with the execution environment, our secrets management service, etc.).

> is this only going to be a SaaS offering

This is another key difference between Relay and StackStorm: We only offer a SaaS right now. That's not to say that we won't eventually offer a self-hosted version (or some sort of hybrid solution for that matter)--it's just the approach we're going with for now.

tbrb · 6 years ago
> every step and trigger in Relay is just a docker container

Ooh, that makes sense. This is also reminding me a bit of Concourse CI (https://concourse-ci.org) as that's all docker-based too, though last I checked it wasn't as kubernetes-native (which I appreciate)

tbrb commented on Show HN: Relay – Event-driven DevOps automation   relay.sh... · Posted by u/product1087
tbrb · 6 years ago
Sounds interesting. Have you any comparisons between this and StackStorm? At first glance, this looks like it competes in a similar market.

Additionally, is this only going to be a SaaS offering, or will we have the option to self-host this as well?

u/tbrb

KarmaCake day6June 25, 2020View Original