[jira] [Updated] (AURORA-1368) shutdown_endpoint fields should be in the aurora schema
[ https://issues.apache.org/jira/browse/AURORA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] brian wickman updated AURORA-1368: -- Story Points: 2 shutdown_endpoint fields should be in the aurora schema --- Key: AURORA-1368 URL: https://issues.apache.org/jira/browse/AURORA-1368 Project: Aurora Issue Type: Task Components: Executor Reporter: brian wickman Assignee: brian wickman Priority: Blocker Commit ea2c9ad24ce adds graceful_shutdown_endpoint and shutdown_endpoint onto the thermos Task object, but Thermos is completely unaware of the http lifecycle. This should either go onto the Job or HealthCheck objects or be added as a separate enumeration on the Job. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1368) shutdown_endpoint fields should be in the aurora schema
[ https://issues.apache.org/jira/browse/AURORA-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] brian wickman updated AURORA-1368: -- Sprint: Twitter Aurora Q2'15 Sprint 6 shutdown_endpoint fields should be in the aurora schema --- Key: AURORA-1368 URL: https://issues.apache.org/jira/browse/AURORA-1368 Project: Aurora Issue Type: Task Components: Executor Reporter: brian wickman Assignee: brian wickman Priority: Blocker Commit ea2c9ad24ce adds graceful_shutdown_endpoint and shutdown_endpoint onto the thermos Task object, but Thermos is completely unaware of the http lifecycle. This should either go onto the Job or HealthCheck objects or be added as a separate enumeration on the Job. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
