Rename STACK_NAME option #63

Closed
opened 2020-12-31 09:03:15 +00:00 by 3wordchant · 1 comment
Owner

From #47:

STACK_NAME should become APP and APP should be used as the main way to refer to an instance of an app all the way down. So the user types abra deploy to do actions on an app and the internals call the stack with the same value as <app>

STACK_NAME -> APP in the compose.yml and .drone.yml references also (this could be something going forward since it is too much busy work to search/replace all this now)

Currently this would break the somewhat-hidden feature where you can set a STACK_NAME that's completely different to the filename, e.g. our gitea instance lives in a file called git.autonomic.zone.env but the STACK_NAME is "gitea".

We could either decide to drop that feature and require that Docker stack names be the same as .env filenames, or fix the naming collision between the <app>$APP argument and the new STACK_NAME 🤔 Any thoughts?

From #47: > `STACK_NAME` should become `APP` and `APP` should be used as the main way to refer to an instance of an app all the way down. So the user types abra <app> deploy to do actions on an app and the internals call the stack with the same value as `<app>` > > `STACK_NAME` -> `APP` in the compose.yml and .drone.yml references also (this could be something going forward since it is too much busy work to search/replace all this now) > Currently this would break the somewhat-hidden feature where you can set a `STACK_NAME` that's completely different to the filename, e.g. our gitea instance lives in a file called `git.autonomic.zone.env` but the `STACK_NAME` is "gitea". > > We could either decide to drop that feature and require that Docker stack names be the same as `.env` filenames, or fix the naming collision between the `<app>` → `$APP` argument and the new `STACK_NAME` 🤔 Any thoughts?
3wordchant added the
breaking-change
enhancement
labels 2020-12-31 09:03:31 +00:00
Owner

Will be discussed in coop-cloud/go-abra#14.

Will be discussed in https://git.autonomic.zone/coop-cloud/go-abra/issues/14.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
2 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/abra#63
No description provided.