Connection to the same target is repetitive right now and requires someone to carefull

Also, I'm not a huge fan of editing global config files like <code class="notranslate"

I came up with a configuration format like this: <div class="highlight highlight-s

Idea: configuration sets about basti HOT 3 CLOSED

basti-app commented on July 23, 2024

Idea: configuration sets

from basti.

Comments (3)

BohdanPetryshyn commented on July 23, 2024

Basti could also search for a configuration file starting from the current working directory and outward. This way, teams could have a basti.json/basti.yaml files with connection targets defined in their repositories instead of polluting package.json with verbose basti commands

from basti.

BohdanPetryshyn commented on July 23, 2024

Also, I'm not a huge fan of editing global config files like ~/.vimrc or ~/.pgpass. It might make sense to wrap the global config file interaction with a Basti command. For example, basti config

from basti.

BohdanPetryshyn commented on July 23, 2024

I came up with a configuration format like this:

---
connect:
  vault-sandbox:
    target: vault-sandbox
    localPort: 8201
  vault-local:
    target: vault-sandbox
    localPort: 8200
  db-main-sandbox:
    target: db-main-sandbox
    localPort: 5432

targets:
  vault-sandbox:
    customTargetVpc: vpc-11111111111111111
    customTargetHost: test-1111111111111111.elb.us-east-1.amazonaws.com
    customTargetPort: 8200
    awsProfile: sandbox
    awsRegion: us-west-1
  db-main-sandbox:
    rds-instance: db-main
    awsProfile: sandbox