Support .env / AWS config file format (aka ini) for local dev

I’d like to propose we additively add support for .env / AWS config file format.

We currently ask people to work locally with a .arc-env file that is unusable by very common tools like dotenv (7mm d/l week).

Although it’s true to the Architect format (with pragmas, keys/values separated by spaces, etc.) It’s another (seemingly proprietary) thing to explain and document.

Having potentially two env formats side by side has been, for me, problematic; it’s bitten me numerous times in personal Arc projects, where my local .env (used for testing individual files, scripts, etc.) was out of sync with my .arc-env, etc.

The ability to tell people to just create a .env file the likes of which closely resembles AWS’s config env feels like it could be a much lower bar and improve interop.

Proposed format:

[testing]
foo=bar
bar=baz
baz=buz

[staging]
foo=bar
bar=baz
# baz=buz commented out

Reference:

• AWS’s parser for this format
• #250

[ryanblock]

Shipped in 8.3!

[ryanblock]

Lol at my “next week!” comment from 7mo ago. It’s in an RC tho, stand by.