Add abra app ls --status to show if app requires an update or not #102

Closed
opened 2021-03-16 06:20:17 +00:00 by decentral1se · 4 comments
Owner

Something like this:

DOMAIN   TYPE   SERVER   STATUS   UPDATE
foo.com  gitea  swarm1  deployed   yes

And then you just run abra app foo.com deploy to specifics (see #90 (comment) for an example of that output).

I would do this but the stuff in sub_app_ls is beyond me (I tried :)).

I think the logic to check if it is an update can copy/pasta or generalise what is over in 16c91fedd1/abra (L530).

Something like this: ``` DOMAIN TYPE SERVER STATUS UPDATE foo.com gitea swarm1 deployed yes ``` And then you just run `abra app foo.com deploy` to specifics (see https://git.autonomic.zone/coop-cloud/abra/issues/90#issuecomment-4251 for an example of that output). I would do this but the stuff in `sub_app_ls` is beyond me (I tried :)). I think the logic to check if it is an update can copy/pasta or generalise what is over in https://git.autonomic.zone/coop-cloud/abra/src/commit/16c91fedd18f46f3844300dc7a845792a831ff29/abra#L530.
decentral1se added this to the Beta release milestone 2021-03-16 06:20:17 +00:00
decentral1se added the
enhancement
label 2021-03-16 06:20:17 +00:00
Author
Owner
Also see https://git.autonomic.zone/coop-cloud/organising/issues/51.
Author
Owner

Coming back to this, if #107 works out and we can make use of the RSS feeds then the logic for this would simply be:

  • look at the deployed container version (7557966c98/abra (L522))
  • look up latest image tag published via RSS feed
  • compare and output
Coming back to this, if https://git.autonomic.zone/coop-cloud/abra/issues/107 works out and we can make use of the RSS feeds then the logic for this would simply be: - look at the deployed container version (https://git.autonomic.zone/coop-cloud/abra/src/commit/7557966c98335f103d907d7aa6eb3e55cd9e6045/abra#L522) - look up latest image tag published via RSS feed - compare and output
Author
Owner

See #113 (comment). We can list versions and make checks to see if updates are available.

See https://git.autonomic.zone/coop-cloud/abra/issues/113#issuecomment-4746. We can list versions and make checks to see if updates are available.
Author
Owner

We tried to crack this but it was a bit hellish and was part of the discussion in coop-cloud/organising#102 which lead us to move away from Bash. This will be handled in go-abra. I've opened up coop-cloud/go-abra#12 to track that.

We tried to crack this but it was a bit hellish and was part of the discussion in [coop-cloud/organising#102](https://git.autonomic.zone/coop-cloud/organising/issues/102) which lead us to move away from Bash. This will be handled in [`go-abra`](https://git.autonomic.zone/coop-cloud/go-abra). I've opened up https://git.autonomic.zone/coop-cloud/go-abra/issues/12 to track that.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 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#102
No description provided.