Flag to support deploying latest git when versions are already published #178

Closed
opened 2021-06-10 09:21:40 +00:00 by decentral1se · 1 comment
Owner

change: ahdinosaur@972ed96, which i got deployed with some manual mucking about. any help on how to learn a development workflow for deploying unofficial versions would be much appreciated.

From https://github.com/Autonomic-Cooperative/traefik/pull/1.

I was thinking, well, if you don't publish a version of your app, it is always using the latest HEAD but if you do publish a version, then you're stuck with that and no way to force it to use latest HEAD again.

#176 will help this from the packaging side. But for the hacking it would be good to have a --chaos so as to override a019417fd2/abra (L604-L608).

I can't really think of a good name for this flag, so I'm just going with --chaos because 🤷‍♀️

> change: ahdinosaur@972ed96, which i got deployed with some manual mucking about. any help on how to learn a development workflow for deploying unofficial versions would be much appreciated. From https://github.com/Autonomic-Cooperative/traefik/pull/1. I was thinking, well, if you don't publish a version of your app, it is always using the latest HEAD but if you do publish a version, then you're stuck with that and no way to force it to use latest HEAD again. https://git.autonomic.zone/coop-cloud/abra/pulls/176 will help this from the packaging side. But for the hacking it would be good to have a `--chaos` so as to override https://git.autonomic.zone/coop-cloud/abra/src/commit/a019417fd2ad42b940ab8d82c708b83398d01658/abra#L604-L608. I can't really think of a good name for this flag, so I'm just going with `--chaos` because 🤷‍♀️
decentral1se added this to the Beta release milestone 2021-06-10 09:21:40 +00:00
decentral1se added the
enhancement
label 2021-06-10 09:21:40 +00:00
Author
Owner

Looks like we have some saucy undocumented behaviour that when you pass dev as the version it does some sort of overriding? I think it does what I am looking for but will add this flag anyway. We can stabilise this later. I want to tweak the deployment overview messages as well.

Looks like we have some saucy undocumented behaviour that when you pass `dev` as the version it does some sort of overriding? I think it does what I am looking for but will add this flag anyway. We can stabilise this later. I want to tweak the deployment overview messages as well.
decentral1se referenced this issue from a commit 2021-06-10 09:40:51 +00:00
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#178
No description provided.