abra create/new/deploy: create a new application #24
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#24
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
We already have
abra deploy
but trying to come at this from a fresh angle with a brand new user in mind. We discussed deploy/update/upgrade as different ways of interacting with an app. All necessary for our thinking for implementation. For this ticket we focus on one user-centric flow: creating a new application.CLI UX proposal
Let's choose one and it will mean to the user: "create a new application"
Implementation proposal
I imagine it to do this under-the-hood. The user runs
abra new wordpress
.mkdir -p ~/.abra/clones/
git clone ...coop-cloud/wordpress ~/.abra/clones/wordpress
abra
reads the~/.abra/clones/wordpress/package.yml
(see coop-cloud/organising#33)abra
displays a bunch of questions and stores the inputs in a~/.abra/$context/$name/app.yml
file where$name
= the name given by the user (e.g. fashion-revolution, should be unique)abra
run as a docker stack deploy and pipes in all the values, creates the secrets etc. and then storesI kinda run out of steam now and Im not sure how this will pan out but I guess we just need to get started and then it will get clearer. There are loads of assumptions littered on this ticket but open to change any.
abra create/new: create a new applicationto abra create/new/deploy: create a new applicationNice UX proposal coming in: