-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENH] Allow commands to be classified into terminating/non-terminating categories #346
Comments
I like this proposal but I would suggest that There are some existing examples of terminating process that I've encountered in the wild, namely testing and linting. One last thought (though I am not yet convinced this is a good idea!): if The |
|
I do quite like that as it makes the most important use case clear... |
|
Someone who is using anaconda-project now extensively for jobs has encountered an issue where they have a project with multiple commands—one intended to run as a persistent deployment, and another is intended to run as a scheduled job.
If you launch the deployment accidentally as a Kubernetes scheduled job, and you also don't know to set your
concurrencyPolicy
for such jobs toReplace
orForbid
, then you have the unfortunate situation that jobs pile up until you exhaust your cluster.It occurs to me that, in the spirit of capturing as much knowledge about a project as possible in anaconda-project.yml, that we could have an optional field that can be added to each command that specifies whether or not it is expected to terminate. For example, we could have a boolean field
terminates
, or a fieldtype
with categoriesapi
,application
,job
, etc.The text was updated successfully, but these errors were encountered: