-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Add aws_ecs_task_definition.proxy_configuration #8780
Conversation
…idelines. resolves #8253
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @SebastianC 👋 Thanks for contributing this! You're off to a good start. Please see the below for some initial feedback and let us know if you have any questions or do not have time to implement the items.
@bflad thanks for the feedback. I hope to get to implementing these changes this week, and will let you know if I have any issues. |
All changes from comments above has been made. Results from unit testing:
Note for this PR:
Also note the failure on:
When I run this against the master I forked from (7acc9ba) I get the same failure. I am unable to validate against the current version of master because I'm running into errors in the Bazaar dependency management tool:
|
I apologize for the delay. I believe this is ready for you to review again. @bflad Please see my notes regarding "d.Set() during the Read operation":
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @SebastianC 👋 Thanks for the updates here. I've provided some followup review items. Hopefully after these we can get this in. Please reach out if you have any questions or do not have time to implement them.
@bflad What is ETA on this pull request? |
@rubycut this is awaiting the community contributor to address the feedback recently provided 2 days ago (#8780 (review)). If there is no response in two weeks, a maintainer will finish it for merge. |
This is ready to review again. @bflad To validate the unit test, I: implemented the changes you mentioned, commented out the "set" operation, ran the unit test, saw the failure you said would happen. un-commented the "set" operation, re-ran the unit tests, and saw the test pass... I think we're good to go there.
CC: @rubycut |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, @SebastianC, thanks so much! 🚀
Output from acceptance testing:
--- PASS: TestAccAWSEcsTaskDefinition_withDockerVolume (13.85s)
--- PASS: TestAccAWSEcsTaskDefinition_constraint (14.51s)
--- PASS: TestAccAWSEcsTaskDefinition_withScratchVolume (14.81s)
--- PASS: TestAccAWSEcsTaskDefinition_arrays (15.41s)
--- PASS: TestAccAWSEcsTaskDefinition_withDockerVolumeMinimalConfig (15.57s)
--- PASS: TestAccAWSEcsTaskDefinition_withNetworkMode (16.79s)
--- PASS: TestAccAWSEcsTaskDefinition_withIPCMode (17.92s)
--- PASS: TestAccAWSEcsTaskDefinition_changeVolumesForcesNewResource (19.93s)
--- PASS: TestAccAWSEcsTaskDefinition_basic (20.29s)
--- PASS: TestAccAWSEcsTaskDefinition_ExecutionRole (23.65s)
--- PASS: TestAccAWSEcsTaskDefinition_Tags (24.04s)
--- PASS: TestAccAWSEcsTaskDefinition_Inactive (25.94s)
--- PASS: TestAccAWSEcsTaskDefinition_Fargate (26.12s)
--- PASS: TestAccAWSEcsTaskDefinition_ProxyConfiguration (28.28s)
--- PASS: TestAccAWSEcsTaskDefinition_withTaskRoleArn (28.67s)
--- PASS: TestAccAWSEcsTaskDefinition_withPidMode (28.96s)
--- PASS: TestAccAWSEcsTaskDefinition_withEcsService (86.30s)
This has been released in version 2.16.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Fixes #8253
Release note for CHANGELOG:
Output from acceptance testing:
Example usage:
I would like some guidance on passing the acceptance tests. when running the acceptance test I get the following error :
testing.go:568: Step 0 error: config is invalid: Unsupported argument: An argument named "proxy_configuration" is not expected here. Did you mean to define a block of type "proxy_configuration"?
and I am unable to see how to resolve this issue.I have confirmed that the proxy configuration applies properly when using
terraform plan
followed byterraform apply
if I build and then switch out aws providers.Here is the full output of the acceptance test: