abra app config -> abra app env edit
#722
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Spin off of #712 from @pharaohgraphy which led to the confusion of thinking "config" was "env vars" because
abra app configedits the env var file 🙃 And in unreleasedabra, thisabra app envsub-command is developing a bit (see below). I like how showabra app config ...is but havingabra app env&abra app configis kind of UI/UX smell. What about decomissioningabra app configand just doingabra app env edit. Thoughts?configis confusing as they are simply Docker env vars, we aren't trying to pull wool over people's eyes and we want this ecosystem to be as transparent & friendly as possible, so I would say we should canabra app config ..completely, and hail the newenvcommand 🙌To note, for backwards compatibility / scripts: I believe it is possible to hide a command from the listing but keep it working. We could add a deprecation warning to
abra app configto point to the new command and eventually migrate away.So it's just a question of UI/UX and hopefully not breaking workflows. This is to be verified if people like the idea.
+0 on this as long as
abra app configremains working (even if hidden) – I would guess "config" is friendlier than "env" for people who aren't super deep into Docker (which isn't a requiredmistakeskill for operators generally), but I agree that having bothconfigandenvis weird.