Implement direnv

[alexrichey]

Never futz with your BUILD_ENGINE or BUILD_ENGINE_SERVER ever again!

Changes

Add .envrc Files

Adds .envrc files to pluto and facilities. These will set up your environment for you, namely:

• make certain paths absolute, which is lovely for things like docker-compose.
• set up your build engine stuff:
  • calculate your schema, based on your branch. (you can override this in the product .envs themselves)
  • so when you cd into products/pluto/ it will set your BUILD_ENGINE_DB to db-pluto, and calculate the build engine, etc.

Add /bash/bin

These are mostly just wrappers around existing bash utils. But this is the preferred way to do it for exporting functions. I think this is a pretty sweet setup... in your terminal you can just type dcp_ and tab-complete to have these fns immediately available. No more sourcing the utils files.

Setup Instructions

Install direnv and make sure to note the requirement to add the direnv hook to your shell.

Then once you cd into a directory with a .envrc you'll need to run direnv allow once to enable direnv.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.00%. Comparing base (b695d9c) to head (00976be).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fvankrieken]

Incredible

Shouldn't the unset be setting it to 'main' instead?

[alexrichey]

you know... I was thinking we'd just never want to build locally against main accidentally. And I suppose you could also just set the BUILD_ENGINE_SCHEMA=main if you wanted to intentionally. But maybe this is a little over-protective

[fvankrieken]

The only way I could love this PR more is if I was staying here longer.

Should we add this for other products? Then just do away with a bunch of the env vars in github actions? I think we could also do away with "bash/build_env_setup.sh"

(Oh though then we'd also need direnv in the build images - a little more work)

[alexrichey]

The only way I could love this PR more is if I was staying here longer.

Should we add this for other products? Then just do away with a bunch of the env vars in github actions? I think we could also do away with "bash/build_env_setup.sh"

(Oh though then we'd also need direnv in the build images - a little more work)

@fvankrieken Yeah, will add for other products next week (feel free to do this without me on Friday though!)