toolshed/abra
4
2
Fork 18
Code Issues 37 Pull Requests 6 Packages Releases 40 Activity

abra 0.10 app deploy output is less informative #550

New Issue
Open
opened 2025-04-24 15:03:57 +00:00 by fauno · 9 comments
fauno commented 2025-04-24 15:03:57 +00:00
Member
Copy Link

previously abra app deploy listed the secrets and configs it was creating or reusing, but now it only shows progress of container deployment. i found the previous output useful to quickly check if the correct version of things was being deployed, specially when doing chaotic stuff.

unsure now if i should get used to it or claim for it to come back :P

coop-cloud/hedgedoc#17 (comment)

previously `abra app deploy` listed the secrets and configs it was creating or reusing, but now it only shows progress of container deployment. i found the previous output useful to quickly check if the correct version of things was being deployed, specially when doing chaotic stuff. unsure now if i should get used to it or claim for it to come back :P https://git.coopcloud.tech/coop-cloud/hedgedoc/pulls/17#issuecomment-24102
👍 2
p4u1 commented 2025-04-24 16:58:29 +00:00
Member
Copy Link

There is some discussion already to add this stuff back. What do you think about only showing this information when it changed? See #537 (comment)

There is some discussion already to add this stuff back. What do you think about only showing this information when it changed? See https://git.coopcloud.tech/toolshed/abra/issues/537#issuecomment-23638
👍 1
fauno commented 2025-04-24 17:25:22 +00:00
Author
Member
Copy Link

showing it when it changes sounds good!

showing it when it changes sounds good!
👍 2
decentral1se commented 2025-04-24 19:34:59 +00:00
Owner
Copy Link

Yeh apologies, I'm kinda freestyling the deploy output and it's still not great IMHO.

All those messages from before are now moved to DEBUG logging messages, so can easily be brought back after "initialising deploy" or whatever it says now. The only issue with "when it changed" is that it only shows when it changes on < v0.10.x? E.g. create/update. So, do we mean that we ignore an "update" (you already know it was created?).

Yeh apologies, I'm kinda freestyling the deploy output and it's still not great IMHO. All those messages from before are now moved to `DEBUG` logging messages, so can easily be brought back after "initialising deploy" or whatever it says now. The only issue with "when it changed" is that it only shows when it changes on < `v0.10.x`? E.g. create/update. So, do we mean that we ignore an "update" (you already know it was created?).
decentral1se added this to the Abra "next" project 2025-04-24 19:35:12 +00:00
decentral1se added the
bug
 label 2025-04-24 19:35:19 +00:00
decentral1se commented 2025-04-25 09:20:06 +00:00
Owner
Copy Link

Merging these two in here:

  • secret versions: #526
  • version of services diff (before deploy) #537

Some stuff is for "before deploy" (overview?) and others for "post deploy" (but we have UI for that yet besides logs).

Merging these two in here: * secret versions: https://git.coopcloud.tech/toolshed/abra/issues/526 * version of services diff (before deploy) https://git.coopcloud.tech/toolshed/abra/issues/537 Some stuff is for "before deploy" (overview?) and others for "post deploy" (but we have UI for that yet besides logs).
decentral1se moved this to Backlog in Abra "next" on 2025-05-11 08:24:52 +00:00
decentral1se commented 2025-05-15 19:48:10 +00:00
Owner
Copy Link

Related: #556

Related: https://git.coopcloud.tech/toolshed/abra/issues/556
3wordchant self-assigned this 2025-06-30 15:00:18 +00:00
decentral1se added the
red abya yala
 label 2025-07-08 10:03:55 +00:00
3wordchant commented 2025-08-05 12:18:35 +00:00
Owner
Copy Link

An attempt at UI design

Original:

➜ abra app deploy foo.bar.example.com
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                NEW DEPLOY OVERVIEW               ┃
┃                                                  ┃
┃ DOMAIN                foo.bar.example.com        ┃
┃ RECIPE                custom-php                 ┃
┃ SERVER                bar.example.com            ┃
┃ CONFIG                compose.yml                ┃
┃                                                  ┃
┃ CURRENT DEPLOYMENT    N/A                        ┃
┃ ENV VERSION           2.0.0+8.4.3-fpm-alpine3.20 ┃
┃ NEW DEPLOYMENT        2.0.0+8.4.3-fpm-alpine3.20 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Secrets

SECRETS    db_password: v1
           db_root_password: v2

Secrets

CONFIGS    entrypoint: v1 → v2

(showing incipient upgrade if possible, otherwise from post-deploy log messages)

Images

IMAGES   app: php:7.4-fpm-alpine3.13 → php:8.4.3-fpm-alpine3.20
         db: mariadb:10.6 (unchanged)
         frontend: nginx:1.20-alpine (unchanged)

But: for long image tags like php:7.4-fpm-alpine3.13 this could make the display Very Wide. Should we break it onto separate lines for upgrades, rather? Or is it rare enough that this is an OK default?

_An attempt at UI design_ Original: ``` ➜ abra app deploy foo.bar.example.com ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ NEW DEPLOY OVERVIEW ┃ ┃ ┃ ┃ DOMAIN foo.bar.example.com ┃ ┃ RECIPE custom-php ┃ ┃ SERVER bar.example.com ┃ ┃ CONFIG compose.yml ┃ ┃ ┃ ┃ CURRENT DEPLOYMENT N/A ┃ ┃ ENV VERSION 2.0.0+8.4.3-fpm-alpine3.20 ┃ ┃ NEW DEPLOYMENT 2.0.0+8.4.3-fpm-alpine3.20 ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ ``` ## Secrets ``` SECRETS db_password: v1 db_root_password: v2 ``` ## Secrets ``` CONFIGS entrypoint: v1 → v2 ``` (showing incipient upgrade if possible, otherwise from post-deploy log messages) ## Images ``` IMAGES app: php:7.4-fpm-alpine3.13 → php:8.4.3-fpm-alpine3.20 db: mariadb:10.6 (unchanged) frontend: nginx:1.20-alpine (unchanged) ``` But: for long image tags like `php:7.4-fpm-alpine3.13` this could make the display Very Wide. Should we break it onto separate lines for upgrades, rather? Or is it rare enough that this is an OK default?
❤️ 2
fauno commented 2025-08-05 12:42:50 +00:00
Author
Member
Copy Link

i like how it shows what's changing!

for logs, i always go to tap since it shows ok / not ok and it's easy to read. maybe something like that, with custom prefixes? what abra version had the INFO/WARN/etc prefixes? i'm not sure i've seen them lately, but i've only been deploying upgrades

i like how it shows what's changing! for logs, i always go to [tap](https://testanything.org/) since it shows ok / not ok and it's easy to read. maybe something like that, with custom prefixes? what abra version had the INFO/WARN/etc prefixes? i'm not sure i've seen them lately, but i've only been deploying upgrades
👀 1
3wordchant commented 2025-08-11 10:21:11 +00:00
Owner
Copy Link

what abra version had the INFO/WARN/etc prefixes? i'm not sure i've seen them lately, but i've only been deploying upgrades

I think current main abra (still?) has those prefixes for abra's own logs:

DEBU <cli/run.go:65> abra version dev, commit a32e30374f402fc00714784b5ee02f845ff27411
...
FATA <recipe/git.go:43> unable to fetch tags in /home/user/.abra/recipes/custom-html: ssh: handshake failed: ssh: disconnect, reason 2: too many authentication failures

For Docker logs (to display after "INFO initialising deployment", I'm not aware of the Docker daemon giving us log-level info; if there is a way of getting it then 💯 it would be great to add those same prefix badges.

Anyway, two ❤️ on the proposed UI I will aim to implement it this week.

> what abra version had the INFO/WARN/etc prefixes? i'm not sure i've seen them lately, but i've only been deploying upgrades I think current `main` abra (still?) has those prefixes for abra's own logs: ``` DEBU <cli/run.go:65> abra version dev, commit a32e30374f402fc00714784b5ee02f845ff27411 ... FATA <recipe/git.go:43> unable to fetch tags in /home/user/.abra/recipes/custom-html: ssh: handshake failed: ssh: disconnect, reason 2: too many authentication failures ``` For Docker logs (to display after "INFO initialising deployment", I'm not aware of the Docker daemon giving us log-level info; if there is a way of getting it then 💯 it would be great to add those same prefix badges. --- Anyway, two ❤️ on [the proposed UI](https://git.coopcloud.tech/toolshed/abra/issues/550#issuecomment-25535) I will aim to implement it this week.
❤️ 1
decentral1se commented 2025-08-11 13:19:05 +00:00
Owner
Copy Link

For Docker logs (to display after "INFO initialising deployment", I'm not aware of the Docker daemon giving us log-level info; if there is a way of getting it then 💯 it would be great to add those same prefix badges.

@3wordchant check out pkg/ui/deploy.go for the gory details! we're receiving all messages from the runtime and decoding and choosing / throwing away some to show on the abra side. i've tried to make more sense of that but it's pretty chaotic... throw in a debug statement somewhere and you'll get a taste for it! Loving the UI developments here 🙏

> For Docker logs (to display after "INFO initialising deployment", I'm not aware of the Docker daemon giving us log-level info; if there is a way of getting it then 💯 it would be great to add those same prefix badges. @3wordchant check out `pkg/ui/deploy.go` for the gory details! we're receiving all messages from the runtime and decoding and choosing / throwing away some to show on the `abra` side. i've tried to make more sense of that but it's pretty chaotic... throw in a debug statement somewhere and you'll get a taste for it! Loving the UI developments here 🙏
👀 1
decentral1se moved this to In Progress in Abra "next" on 2025-08-12 05:22:16 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
build
go build related issues
ci/cd
Building things with CI/CD
contributing
Dealing with contributing
critical fix
https://docs.coopcloud.tech/federation/resolutions/passed/010/
design
UI/UX
documentation
Documenting all the things
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
meta
relating to the project or repo itself
question
More information is needed
red abya yala
Work funded by Calyx institute for Red Abya Yala
release
Release management
release-candidate
Related to the new release candidate
security
Security related
test
Unit/integration testing
wontfix
This won't be fixed
No Label
bug
red abya yala
Milestone
No items
No Milestone
Projects
Clear projects
No project Abra "next"
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas coopcloud decentral1se fauno jmakdah2 kawaiipunk knoflook lambdabundesverband moritz p4u1 ripclap simon sixsmith trav val yksflip
No Assignees 3wordchant
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#550
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?