oxheadalpha / teztnets

https://teztnets.xyz
21 stars 26 forks source link

jobs should be deleted and recreated if new values are made #138

Open orcutt989 opened 1 year ago

orcutt989 commented 1 year ago

We made changes to the rollup node values https://github.com/oxheadalpha/teztnets/commit/f58b3cfde0829cc31d8c3509ffdc3fbe07aef985 and the actdivation job did not clear out and restart causing us to manually have to delete and create a new job on the cluster.

Expected functionality should be if a job is dependent on a value it should be deleted and restarted to prevent this manual intervention.

harryttd commented 1 year ago

It isn't possible without replacing the whole job. I looked it up again to confirm https://serverfault.com/questions/809632/is-it-possible-to-rerun-kubernetes-job

orcutt989 commented 1 year ago

Thanks. What I mean is we should have a mechanism of some sort that deletes and recreates jobs, not necessarily literally restart the exact job again. We do this with xtz-shots.

harryttd commented 1 year ago

this may be possible with deleteBeforeReplace on the job https://www.pulumi.com/docs/concepts/options/deletebeforereplace/#:~:text=Resource%20option%3A%20deleteBeforeReplace&text=By%20default%2C%20to%20minimize%20downtime,resource%20before%20creating%20its%20replacement.