Support environment variables syntax in settings (Craft 3.1)

[timkelty]

craftcms/cms#3219 (comment)

The goal is to be able to use env vars for things that would change per-env…which is pretty much everything (bucket, region, keyId, secret, url)

[michaelroper]

This would probably (hopefully) solve this issue too? craftcms/cms#3531

[brandonkelly]

Right, they are one and the same.

[michaelroper]

Hey @brandonkelly - I noticed that this is fixed in the 3.1 branch... doe that mean i can point Composer to use the dev-craft-3.1 version instead of the master/release package?

(I know you said you were still working on making it possible to release 3.1-only versions of plugins..)

[baileydoestech]

Would second getting the release of this now that Craft 3.1 is out (don't want our AWS secrets stored in source control), is there an ETA?

[carlcs]

craft-3.1 branch doesn’t seem to be ready yet @michaelroper

[michaelroper]

@carlcs "craftcms/aws-s3": "dev-craft-3.1" has been working okay for me? ¯_(ツ)_/¯

[carlcs]

@michaelroper strange, for me it’s showing the value of the env vars in the input fields after save

[michaelroper]

Do you still have settings in a config/volumes.php? Because they will override and insert themselves into the DB..

[carlcs]

You mean „environment variables make their way into the yaml when settings are saved via web“?

craftcms/cms#3655

…thanks @michaelroper, I‘ll check tomorrow but I am pretty sure I forgot about the configuration file.

[michaelroper]

np - was just catching up on your conversation with ben in slack too... you were heading in the right direction!

[boboldehampsink]

Need this too, thanks

[andris-sevcenko]

Just to check in, guys - going over all the plugins to see if there are any outstanding releases and/or 3.1 issues that need to be resolved is on my list.

Just still dealing with a little bit of post-3.1-crazy here.

[boboldehampsink]

Np, I just submitted some also as a reminder to myself (and that I can reference to in my own projects).

[carlcs]

🎉