Sebastian Millius
03/28/2024, 8:03 AMflytectl register
is not an atomic operation / transaction. It starts registering but aborts when failing on a workflow and ends up in this half deployed state. Is it possible for flytectl to rollback in that case? Or do first pre-checks and only register if all checks pass?
• We are using reference tasks heavily and when registering all workflows, we'd need to make sure we register in the correct topological order as flytectl register will check that reference tasks are there. Is there a way to take the workflows just to be registered also into account or disable that check?
• Is there a way to register multiple archives at once?
• I see that --force
can be used to forcefully set the version for all entities to be registered and that seems to also apply to reference tasks. Is there a way to also set project/domain on the referenced tasks? This is because we'd deploy for testing into a separate project/domain.
I can solve these problems by:
• Manually merging the tgz files for all my workflows
• Topologically order the entries so that I register the workflows first that are referenced later as reference tasks
• Overwrite the project/domain/version in the protos specifying called reference tasks manually
But I was just wondering whether there's an easier way around that.Ketan (kumare3)
Sebastian Millius
03/28/2024, 2:39 PMKetan (kumare3)
Ketan (kumare3)
Ketan (kumare3)
Ketan (kumare3)
Ketan (kumare3)
infinite
we can completely shard the db and it should absolutely be fine