Add a task for switching between environments

[lipskis]

This is what I use to quickly switch between different environments. I run rake env:local or rake env:staging, or rake env:prod and that's it.

It's basically just 3 appsignal_key_[env].env files, and an .appsignal_environment file that tracks which env file is used in appsignal_key.env. A command like rake env:local copies appsignal_key_local.env to appsignal_key.env, which then gets used in all test-setups.

I haven't made this work with rake global:set_push_api_key, but I will do that if this is something that we actually want to add.

[backlog-helper]

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

[unflxw]

CI failure unrelated, fixed in #364.

[unflxw]

Something like this would be nice, yes! Here are some non-binding thoughts:

Wondering if we could have it print the whole contents of appsignal_key.env on boot, and then we don't need to keep around .appsignal_environment for that purpose (which is a piece of state that may fall out of sync with the state it's supposed to correlate to) -- the file could have a # ENV: prod comment added at the top of it when you switch.

I think giving the implementation another spin could work. Replacing global:set_push_api_key or getting rid of it entirely seems necessary, yes.

I'd suggest not having aliases that don't match the required file names. If the file has to be named _local.env, don't let me use env:development, that only makes it more confusing when I name the file _development.env and it doesn't work.

Consider replacing the three tasks with a parameter? Something like rake env=prod env:switch replacing all three, for example. That way there's no mandatory set of allowed names.

[backlog-helper]

• This Pull Request has been approved. Can it be merged @lipskis? - (More info)

---

This is a message from the daily scheduled checks.

New issue guide | Backlog management | Rules | Feedback