coop-cloud/abra
coop-cloud
/
abra
Archived
7
0
Fork 2
Code Issues 21 Pull Requests Releases Activity

Versioning roadmap guidance #90

New Issue
Closed
opened 2021-03-08 08:32:43 +00:00 by decentral1se · 7 comments
decentral1se commented 2021-03-08 08:32:43 +00:00
Owner
Copy Link

We need to read coop-cloud/organising#48 (comment) and come up with ways to suit those workflows and then bake them into abra. Leaving this as a place holder for now. Lots of open questions.

We need to read https://git.autonomic.zone/coop-cloud/organising/issues/48#issue-1011 and come up with ways to suit those workflows and then bake them into `abra`. Leaving this as a place holder for now. Lots of open questions.
decentral1se added the
design
 label 2021-03-08 08:32:43 +00:00
decentral1se commented 2021-03-08 15:43:04 +00:00
Author
Owner
Copy Link

If abra app ls could show 1. deployed version 2. upstream app repo version then it would be much easier to know what needs to be updated. Our current internal setup has 29 apps and it is impossible to tell without manually checking now.

This involves us tagging each app in the repo following this guide coop-cloud/organising#34 (comment) and then abra can do the above work.

If `abra app ls` could show 1. deployed version 2. upstream app repo version then it would be much easier to know what needs to be updated. Our current internal setup has 29 apps and it is impossible to tell without manually checking now. This involves us tagging each app in the repo following this guide https://git.autonomic.zone/coop-cloud/organising/issues/34#issuecomment-4058 and then `abra` can do the above work.
decentral1se commented 2021-03-08 15:44:40 +00:00
Author
Owner
Copy Link

https://chat.internal.autonomic.zone/channel/projects.coopcloud?msg=KJEdhHTkF2niMJmWk

so far we get automated notifications of the upstream-upstream updates (e.g. Wordpress 5.1.2 -> 5.1.3 or whatever), but we don't yet have automation for redeploying our apps after that's happened
at the moment the Extra Manual process would be:

  1. Wordpress releases new upstream update
  2. renovate-bot alerts us to the new Docker image
  3. One of us merges the renovate-bot PR to update the Co-op Cloud app definition
  4. NEW STEP: that same person does abra app ls | grep wordpress and then runs abra app ... deploy --update on all those apps
https://chat.internal.autonomic.zone/channel/projects.coopcloud?msg=KJEdhHTkF2niMJmWk > so far we get automated notifications of the upstream-upstream updates (e.g. Wordpress 5.1.2 -> 5.1.3 or whatever), but we don't yet have automation for redeploying our apps after that's happened > at the moment the Extra Manual process would be: > 1. Wordpress releases new upstream update > 2. renovate-bot alerts us to the new Docker image > 3. One of us merges the renovate-bot PR to update the Co-op Cloud app definition > 4. NEW STEP: that same person does abra app ls | grep wordpress and then runs abra app ... deploy --update on all those apps
decentral1se commented 2021-03-08 16:00:54 +00:00
Author
Owner
Copy Link

OK smashing. I'll see about hacking the label lookup into abra app ls --status as a route to updating the apps which need it rn. and then do the drone-abra-deploy after

So, a drone plugin that can roll auto-updates assuming we have monitoring up for those apps. Annnddd the ability for abra to tell us what needs updating seems to be a plan in the works!

> OK smashing. I'll see about hacking the label lookup into abra app ls --status as a route to updating the apps which need it rn. and then do the drone-abra-deploy after So, a drone plugin that can roll auto-updates assuming we have monitoring up for those apps. Annnddd the ability for abra to tell us what needs updating seems to be a plan in the works!
3wordchant commented 2021-03-10 21:17:07 +00:00
Owner
Copy Link

Another idea that was raised was abra app --all deploy --update, which I think might be a big help to people using abra solo (as opposed to our monorepo style).

Another idea that was raised was `abra app --all deploy --update`, which I think might be a big help to people using `abra` solo (as opposed to our monorepo style).
👍 1
decentral1se commented 2021-03-10 21:46:46 +00:00
Author
Owner
Copy Link

More relevant thoughts forming in coop-cloud/organising#47.

More relevant thoughts forming in https://git.autonomic.zone/coop-cloud/organising/issues/47.
decentral1se added this to the Beta release milestone 2021-03-11 20:12:54 +00:00
decentral1se commented 2021-03-15 17:35:59 +00:00
Author
Owner
Copy Link

OK, current WIP version handling output is the following:

➜  abra (main) ✔ abra app git.autonomic.zone deploy
Deployment overview:                         
  Server: swarm.autonomic.zone
  Compose: /home/decentral1se/.abra/apps/gitea/compose.yml
  Domain: git.autonomic.zone
  App type: gitea
  Versions:
    gitea_app (gitea/gitea):
      deployed: 1.13.4 (078f8918)
      to de deployed: 1.13.5 (078f8918)
    gitea_db (mariadb):
      deployed: 10.5 (e27cf5bc)
ERROR: A new app state will be deployed! Please use --update to consent

(EDIT: updated output)

OK, current WIP version handling output is the following: ``` ➜ abra (main) ✔ abra app git.autonomic.zone deploy Deployment overview: Server: swarm.autonomic.zone Compose: /home/decentral1se/.abra/apps/gitea/compose.yml Domain: git.autonomic.zone App type: gitea Versions: gitea_app (gitea/gitea): deployed: 1.13.4 (078f8918) to de deployed: 1.13.5 (078f8918) gitea_db (mariadb): deployed: 10.5 (e27cf5bc) ERROR: A new app state will be deployed! Please use --update to consent ``` (EDIT: updated output)
decentral1se commented 2021-03-16 06:23:14 +00:00
Author
Owner
Copy Link

OK, I am gonna close this off here in abra land in favour of #102 which covers "when do we know we need to make an update" with a manual workflow. We can keep brainstorming from coop-cloud/organising#48.

OK, I am gonna close this off here in `abra` land in favour of https://git.autonomic.zone/coop-cloud/abra/issues/102 which covers "when do we know we need to make an update" with a manual workflow. We can keep brainstorming from https://git.autonomic.zone/coop-cloud/organising/issues/48.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
main
requirements-install-script
prefer-fast-option
add-bump-logic
prompt-cleanup
fix-pwgen
fix-subcommand-select
digest-version
backup_restore
command_help_2
merge-logging
monorepo
10.0.0
9.0.0
8.0.1
8.0.0
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
checkout
0.6.0
0.5.0
0.4.1
0.4.0
0.3.1
0.3.0
0.2.0
0.1.2
0.1.1
0.1.0
Labels
Clear labels   
breaking-change

Anything that breaks the existing API

  
bug

Something is not working

  
CI/CD

Anything to do with testing and infra

  
design

Anything to with UX of this tool

  
documentation

Documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
plugin

Related to the plugin architecture

  
question

More information is needed

  
secrets

Everything to do with docker secrets

  
shell-completion

To do with shell completion

  
versioning

All the things to do with versioning apps

  
wontfix

This won't be fixed

No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
Milestone
Clear milestone
No items
No Milestone
Beta release
Assignees
Clear assignees
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#90
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?