Delete collection-continuous-integration.yml #7
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
We're not using GH workflows
gundalow
approved these changes
Mar 18, 2020
jillr
pushed a commit
to jillr/amazon.aws
that referenced
this pull request
May 3, 2021
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
jillr
pushed a commit
to jillr/amazon.aws
that referenced
this pull request
May 10, 2021
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
jillr
pushed a commit
to jillr/amazon.aws
that referenced
this pull request
May 10, 2021
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
jillr
pushed a commit
to jillr/amazon.aws
that referenced
this pull request
May 13, 2021
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Sep 18, 2023
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Sep 18, 2023
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this pull request
Oct 24, 2023
…-collections#7) It is possible for all instances to stop matching the filters between the initial check for existing instances and the first call to find_instances() in change_instance_state(). If this happened, find_instances() would previously be called a second time with an empty list of instance IDs and no filters, which should not happen and immediately ends module execution with the error "No filters provided when they were required".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SUMMARY
We're not using GH workflows
ISSUE TYPE
COMPONENT NAME
.github
ADDITIONAL INFORMATION
Supersedes #3 as the rebase was pretty bad there