#geodesic (2022-09)

geodesic https://github.com/cloudposse/geodesic

Discussions related to https://github.com/cloudposse/geodesic

Archive: https://archive.sweetops.com/geodesic/

2022-09-07

Release notes from geodesic avatar
Release notes from geodesic
03:20:42 AM

v1.2.4 Included Tools Update AWS CLI packages @renovate (<a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1330601562” data-permission-text=”Title is private” data-url=”https://github.com/cloudposse/geodesic/issues/797“…

Release v1.2.4 · cloudposse/geodesicattachment image

Included Tools Update AWS CLI packages @renovate (#797) This PR contains the following updates: Package Change Age Adoption Passing Confidence awscli (source, changelog) ==1.25.43 -> ==…

renovate - Overview

renovate has one repository available. Follow their code on GitHub.

Update AWS CLI packages by renovate[bot] · Pull Request #797 · cloudposse/geodesicattachment image

This PR contains the following updates: Package Change Age Adoption Passing Confidence awscli (source, changelog) ==1.25.43 -> ==1.25.69 boto3 ==1.24.43 -> ==1.24.68 Release No…

2022-09-08

Release notes from geodesic avatar
Release notes from geodesic
08:50:40 PM

v1.3.0 Notable change: Preserve Dockerfile PATH Notable change Debian behavior is to ignore any existing value of the PATH environment variable when launching bash and set it to a predefined value. This makes it impossible to modify the PATH in the Dockerfile. Alpine’s approach (taken from Arch Linux) is to append the path components to any existing PATH value, allowing users to set a preferred path, but still ensuring that all expected/required directories are included in PATH to start. In this release, we follow Alpine’s strategy under…

Release v1.3.0 Notable change: Preserve Dockerfile PATH · cloudposse/geodesicattachment image

Notable change Debian behavior is to ignore any existing value of the PATH environment variable when launching bash and set it to a predefined value. This makes it impossible to modify the PATH in …

2022-09-15

Matt Gowie avatar
Matt Gowie

Hey @Jeremy G (Cloud Posse) — low priority, but a couple quick questions for you following some internal discussion at Masterpoint on Geodesic.

  1. In Dockerfile.options, you folks mention preferring YAML configuration direnv>. My assumption is that you’re referring to things like terraform vars and similar configuration that atmos now covers, but not for actual environment variables. Is that correct? My team and I are working on setting env vars like KUBECONFIG + AWS_CONFIG_FILE to custom, project specific files via direnv. And before we do so I figured I would ask about that comment considering ya’ll might have some learnings there.
  2. Do you have a suggested approach for running direnv allow $GEODESIC_HOST_CWD/.envrc on start of the container? I don’t want to use a preferences or overrides file because we want it to be persisted across all container sessions and not just my own. I’m assuming that means we need to add an additional bash script into rootfs/ that’ll get executed by Geodesic at start of the container, but I’m unaware what would be the best option there as I’d rather not override /etc/profile completely.
# Our older Geodesic configurations relied on `direnv`, which we no longer recommend,
# preferring YAML configuration files instead.
Jeremy G (Cloud Posse) avatar
Jeremy G (Cloud Posse)

I will ask @Erik Osterman (Cloud Posse) to weigh in here, as he was the original direnv proponent and set up all of Geodesic’s direnv support.

Our current model is to use Geodesic tools against files on the host computer, mounted into the container at /localhost. This can be tricky with direnv allow, either being a hassle or a security weakness depending on your configuration and point of view. Personally I prefer setting env vars via shell scripts and functions, either run at startup or explicitly on the command line.

You can add scripts under rootfs/etc/profile.d/ in your repo. Any file in that directory ending in .sh will be sourced by bash at shell startup. Since Geodesic comes with a direnv.sh which you do not want to overwrite, you might call your script direnv_allow_host.sh and put

direnv allow $GEODESIC_HOST_CWD/.envrc

in it.

# Our older Geodesic configurations relied on `direnv`, which we no longer recommend,
# preferring YAML configuration files instead.
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Ya, we really haven’t invested too much more in this b/c it’s an interactive shell thing and we’ve been moving gitops

1
Matt Gowie avatar
Matt Gowie

Good stuff — Thanks gents!

    keyboard_arrow_up