Skip to content
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 resource for an ELB SSL negotiation policy #8084

Merged
merged 6 commits into from
Aug 11, 2016

Conversation

bigkraig
Copy link
Contributor

@bigkraig bigkraig commented Aug 9, 2016

This is basically a dupe of #5637 but @fpmosley didn't have the bandwidth to rebase.

Mosley, Franklin added 5 commits August 9, 2016 15:29
Added new resource to create an AWS ELB SSL negotiation policy, and an
acceptance test.
Updated the Terraform documentation to add a new page, and a link in
the sidebar, for the aws_lb_ssl_negotiation_policy resource.
Changed the `attribute` argument of the resource to be optional vs.
required.
Corrected printf verb by changing it from a string type to an int type.
@stack72
Copy link
Contributor

stack72 commented Aug 9, 2016

Fixes #2171 / Fixes #3176

@stack72
Copy link
Contributor

stack72 commented Aug 10, 2016

Hey @bigkraig

Thanks so much for the rebase here - the test doesn't work I'm afraid :(

% make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSLBSSLNegotiationPolicy'
==> Checking that code complies with gofmt requirements...
/Users/stacko/Code/go/bin/stringer
go generate $(go list ./... | grep -v /terraform/vendor/)
2016/08/10 11:58:56 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSLBSSLNegotiationPolicy -timeout 120m
=== RUN   TestAccAWSLBSSLNegotiationPolicy_basic
--- FAIL: TestAccAWSLBSSLNegotiationPolicy_basic (12.81s)
    testing.go:264: Step 0 error: Error applying: 1 error(s) occurred:

        * aws_iam_server_certificate.test_cert: [WARN] Error uploading server certificate, error: MalformedCertificate: Certificate is no longer valid. The 'Not After' date restriction on the certificate has passed.
FAIL
exit status 1
FAIL    github.com/hashicorp/terraform/builtin/providers/aws    12.832s
make: *** [testacc] Error 1

Any chance you could have a look?

P.

@stack72 stack72 added the waiting-response An issue/pull request is waiting for a response from the community label Aug 10, 2016
@jamesdehart
Copy link

Seems it might be just bad test data.

@fpmosley
Copy link

@bigkraig @stack72 The Acceptance Test fails because it is using an expired certificate that was lifted from:
builtin/providers/aws/resource_aws_iam_server_certificate_test.go

The certs were fixed in this commit:
005d9a1

Just take the certs from there and it should work.

@bigkraig
Copy link
Contributor Author

@stack72 I've updated the test data and it looks good

Kraigs-MacBook-Pro:terraform kamador$ make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSLBSSLNegotiationPolicy'
==> Checking that code complies with gofmt requirements...
/Users/kamador/gocode/bin/stringer
go generate $(go list ./... | grep -v /terraform/vendor/)
2016/08/10 13:30:32 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSLBSSLNegotiationPolicy -timeout 120m
=== RUN   TestAccAWSLBSSLNegotiationPolicy_basic
--- PASS: TestAccAWSLBSSLNegotiationPolicy_basic (27.99s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    28.009s

@fpmosley
Copy link

@bigkraig Looks like you were already on top of it fixing it. Great!

@stack72
Copy link
Contributor

stack72 commented Aug 11, 2016

@bigkraig this looks good to me now :) Thanks so much! - just manually merged this!

@gokul-p
Copy link

gokul-p commented Aug 11, 2016

This fix will be included in next release ? whats plan for next release ?

@stack72
Copy link
Contributor

stack72 commented Aug 11, 2016

Hi @gokul-p

yes this will be included for 0.7.1 - there is no formal release date yet

Paul

@gokul-p
Copy link

gokul-p commented Aug 12, 2016

thanks @stack72 - Please update me,once you have the date.

@41jules1967
Copy link

41jules1967 commented Oct 31, 2016

This seems to be in place but I can't tell if it's working.
The console screens don't make any reference to the new policy and imply the ELB is using the default policy.
Is it actually working?

@ghost
Copy link

ghost commented Apr 20, 2020

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 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.
Labels
enhancement provider/aws waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants