-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/aws: Add CertificateNotFound retry waiter to aws_alb_listener #10180
Merged
stack72
merged 1 commit into
hashicorp:master
from
paybyphone:pbp_b_alb_listener_certnotfound_retry
Nov 17, 2016
Merged
provider/aws: Add CertificateNotFound retry waiter to aws_alb_listener #10180
stack72
merged 1 commit into
hashicorp:master
from
paybyphone:pbp_b_alb_listener_certnotfound_retry
Nov 17, 2016
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
Looks like sometimes it takes some time for IAM certificates to propagate, which can cause errors on ALB listener creation. Possibly same thing as hashicorp#5178, but for ALB now instead of ELB. This was discovered via acceptance tests, specifically the TestAccAWSALBListener_https test. Updated the creation process to wait on CertificateNotFound for a max of 5min.
vancluever
pushed a commit
to paybyphone/terraform
that referenced
this pull request
Nov 17, 2016
This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until hashicorp#10180 is merged.
Hi @vancluever this LGTM! Thanks for this - this was definitely an annoying bug
|
stack72
pushed a commit
that referenced
this pull request
Nov 17, 2016
#10180) Looks like sometimes it takes some time for IAM certificates to propagate, which can cause errors on ALB listener creation. Possibly same thing as #5178, but for ALB now instead of ELB. This was discovered via acceptance tests, specifically the TestAccAWSALBListener_https test. Updated the creation process to wait on CertificateNotFound for a max of 5min.
jrnt30
pushed a commit
to jrnt30/terraform
that referenced
this pull request
Nov 17, 2016
hashicorp#10180) Looks like sometimes it takes some time for IAM certificates to propagate, which can cause errors on ALB listener creation. Possibly same thing as hashicorp#5178, but for ALB now instead of ELB. This was discovered via acceptance tests, specifically the TestAccAWSALBListener_https test. Updated the creation process to wait on CertificateNotFound for a max of 5min.
vancluever
pushed a commit
to paybyphone/terraform
that referenced
this pull request
Nov 17, 2016
This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until hashicorp#10180 is merged.
stack72
pushed a commit
that referenced
this pull request
Nov 18, 2016
* provider/aws: Add aws_alb_listener data source This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until #10180 is merged. * provider/aws: Add aws_alb_listener data source docs Now documented.
stack72
pushed a commit
that referenced
this pull request
Nov 18, 2016
* provider/aws: Add aws_alb_listener data source This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until #10180 is merged. * provider/aws: Add aws_alb_listener data source docs Now documented.
gusmat
pushed a commit
to gusmat/terraform
that referenced
this pull request
Dec 6, 2016
hashicorp#10180) Looks like sometimes it takes some time for IAM certificates to propagate, which can cause errors on ALB listener creation. Possibly same thing as hashicorp#5178, but for ALB now instead of ELB. This was discovered via acceptance tests, specifically the TestAccAWSALBListener_https test. Updated the creation process to wait on CertificateNotFound for a max of 5min.
gusmat
pushed a commit
to gusmat/terraform
that referenced
this pull request
Dec 6, 2016
* provider/aws: Add aws_alb_listener data source This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until hashicorp#10180 is merged. * provider/aws: Add aws_alb_listener data source docs Now documented.
fatmcgav
pushed a commit
to fatmcgav/terraform
that referenced
this pull request
Feb 27, 2017
hashicorp#10180) Looks like sometimes it takes some time for IAM certificates to propagate, which can cause errors on ALB listener creation. Possibly same thing as hashicorp#5178, but for ALB now instead of ELB. This was discovered via acceptance tests, specifically the TestAccAWSALBListener_https test. Updated the creation process to wait on CertificateNotFound for a max of 5min.
fatmcgav
pushed a commit
to fatmcgav/terraform
that referenced
this pull request
Feb 27, 2017
* provider/aws: Add aws_alb_listener data source This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until hashicorp#10180 is merged. * provider/aws: Add aws_alb_listener data source docs Now documented.
grubernaut
pushed a commit
to hashicorp/terraform-provider-aws
that referenced
this pull request
Jun 9, 2017
* provider/aws: Add aws_alb_listener data source This adds the aws_alb_listener data source to get information on an AWS Application Load Balancer listener. The schema is slightly modified (only option-wise, attributes are the same) and we use the aws_alb_listener resource read function to get the data. Note that the HTTPS test here may fail due until hashicorp/terraform#10180 is merged. * provider/aws: Add aws_alb_listener data source docs Now documented.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Apr 20, 2020
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.
Looks like sometimes it takes some time for IAM certificates to
propagate, which can cause errors on ALB listener creation.
Possibly same thing as #5178, but for ALB
now instead of ELB.
This was discovered via acceptance tests, specifically the
TestAccAWSALBListener_https
test. Updated the creation process to waiton
CertificateNotFound
for a max of 5min.