This repository has been archived by the owner on Nov 12, 2019. It is now read-only.
Include internal state provisioner #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
jhford
added a commit
to taskcluster/taskcluster-tools
that referenced
this pull request
Aug 23, 2016
|
taskcluster/taskcluster-tools#132 see also |
|
This broke the UI... |
|
|
jhford
added a commit
to taskcluster/taskcluster-tools
that referenced
this pull request
Aug 25, 2016
Corresponding change for taskcluster/aws-provisioner#114
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This includes c772d4d which is a fix to the fallout from today's deployment's issue.
The rest of this patch is to include the internally tracked EC2 spot instance requests in the provisioner state apis. The new parameter
visibleToEC2Apiwill tell us whether the instance is included in the crappy API lag situation we get.