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
Enable Task to accept externally generated task id #115
Comments
Once spring-cloud/spring-cloud-dataflow#492 is merged we could have a chat about this implementation in more detailed level. |
spring-cloud/spring-cloud-dataflow#492 is now merged |
@mminella so only integration from tasks towards this deployment id repository is TaskDeploymentController.java#L153 Similarly we now have an option to do more clever cancel(undeploy in stream): And possibly querying status from deployer point of view if task is not yet running(shell status for stream): I think this thing around execution id becomes more clear if/when we try to implement those cancel()/status() features from tasks side towards |
resolves spring-cloud#115 * Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire. * Updated docs * Removed deprecation * Fixed version number for integration test. Added integration tests for externally generated task executions
resolves spring-cloud#115 * Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire. * Updated docs * Removed deprecation * Fixed version number for integration test. Added integration tests for externally generated task executions
resolves spring-cloud#115 * Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire. * Updated docs * Removed deprecation * Fixed version number for integration test. Added integration tests for externally generated task executions
resolves spring-cloud#115 * Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire. * Updated docs * Removed deprecation * Fixed version number for integration test. Added integration tests for externally generated task executions Add externalExecutionId resolves spring-cloud#80
resolves #115 * Fixes bug where if the user set the environment variable and commandline args a unique constraint would fire. * Updated docs * Removed deprecation * Fixed version number for integration test. Added integration tests for externally generated task executions Add externalExecutionId resolves #80
In order to allow for the time difference between when a task is requested and the infrastructure actually launches it, we'll need to be able to map the infrastructure's execution id with the task execution id. This story is to allow that mapping to occur by having the launcher do the creation of the task execution record within the task repository.
The text was updated successfully, but these errors were encountered: