-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
AWS Batch Compute Environment add update_policy
parameter
#34353
AWS Batch Compute Environment add update_policy
parameter
#34353
Conversation
Community NoteVoting for Prioritization
For Submitters
|
Hey @drewmullen 👋 Thank you very much for your contribution! At times, our maintainers need to make direct edits to pull requests in order to help get it ready to be merged. Your current settings do not allow maintainers to make such edits. To help facilitate this, update your pull request to allow such edits as described in GitHub's Allowing changes to a pull request branch created from a fork documentation. (If you're using a fork owned by an organization, your organization may not allow you to change this setting. If that is the case, let us know.) |
update_policy
parameterupdate_policy
parameter
143e24e
to
d32f491
Compare
d32f491
to
a2fa6bf
Compare
update_policy
parameterupdate_policy
parameter
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.
LGTM 🚀
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! I wasn't able to commit to the downstream branch, so left a couple suggestions with what I'd changed locally. Just one small typo/logging fix and a documentation fix.
Will run the full test suite and merge after the changes go through.
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
@jar-b how did you do multi-line `suggestion boxes? |
Also, going foward we wont use orgs for PR sources and instead will use personal repos. That is whats preventing you from committing back upstream - apologies for that |
Just to the left of the -/+ diff markers there is a blue box you can drag across multiple lines. |
No problem - thanks for getting the changes in. Running tests now. |
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.
LGTM 🎉
% make testacc PKG=batch TESTS="TestAccBatchComputeEnvironment_|TestAccBatchComputeEnvironmentDataSource_"
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/batch/... -v -count 1 -parallel 20 -run='TestAccBatchComputeEnvironment_|TestAccBatchComputeEnvironmentDataSource_' -timeout 360m
--- PASS: TestAccBatchComputeEnvironment_createUnmanagedWithComputeResources (4.51s)
=== CONT TestAccBatchComputeEnvironment_UpdateSecurityGroupsAndSubnets_fargate
--- PASS: TestAccBatchComputeEnvironment_createEC2WithoutComputeResources (32.74s)
=== CONT TestAccBatchComputeEnvironment_ec2Configuration
--- PASS: TestAccBatchComputeEnvironment_createFargate (37.77s)
=== CONT TestAccBatchComputeEnvironment_updateLaunchTemplate
--- PASS: TestAccBatchComputeEnvironmentDataSource_basic (40.38s)
=== CONT TestAccBatchComputeEnvironment_ComputeResources_maxVCPUs
--- PASS: TestAccBatchComputeEnvironment_CreateSpotAllocationStrategy_bidPercentage (52.92s)
=== CONT TestAccBatchComputeEnvironment_launchTemplate
=== CONT TestAccBatchComputeEnvironment_updatePolicyUpdate
--- PASS: TestAccBatchComputeEnvironment_disappears (52.99s)
--- PASS: TestAccBatchComputeEnvironmentDataSource_basicUpdatePolicy (54.44s)
=== CONT TestAccBatchComputeEnvironment_defaultServiceRole
=== NAME TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags
compute_environment_test.go:481: Step 1/2 error: After applying this test step and performing a `terraform refresh`, the plan was not empty.
stdout
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# aws_batch_compute_environment.test will be updated in-place
~ resource "aws_batch_compute_environment" "test" {
id = "tf-acc-test-8202777925839378489"
tags = {}
# (9 unchanged attributes hidden)
~ compute_resources {
~ desired_vcpus = 4 -> 8
tags = {
"key1" = "value1"
}
# (10 unchanged attributes hidden)
# (1 unchanged block hidden)
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
--- PASS: TestAccBatchComputeEnvironment_createEC2 (64.28s)
=== CONT TestAccBatchComputeEnvironment_updateServiceRole
--- PASS: TestAccBatchComputeEnvironment_nameGenerated (65.61s)
=== CONT TestAccBatchComputeEnvironment_basic
--- PASS: TestAccBatchComputeEnvironment_namePrefix (66.60s)
--- PASS: TestAccBatchComputeEnvironment_createFargateSpot (67.08s)
--- PASS: TestAccBatchComputeEnvironment_ec2ConfigurationPlacementGroup (68.61s)
--- PASS: TestAccBatchComputeEnvironment_updateState (70.35s)
--- PASS: TestAccBatchComputeEnvironment_ec2Configuration (38.36s)
--- PASS: TestAccBatchComputeEnvironment_UpdateSecurityGroupsAndSubnets_fargate (73.23s)
--- PASS: TestAccBatchComputeEnvironment_tags (78.15s)
--- PASS: TestAccBatchComputeEnvironment_updatePolicyCreate (85.95s)
--- PASS: TestAccBatchComputeEnvironment_defaultServiceRole (32.77s)
--- PASS: TestAccBatchComputeEnvironment_launchTemplate (35.03s)
--- PASS: TestAccBatchComputeEnvironment_basic (29.76s)
--- PASS: TestAccBatchComputeEnvironment_updateLaunchTemplate (59.30s)
--- PASS: TestAccBatchComputeEnvironment_updatePolicyUpdate (45.57s)
--- PASS: TestAccBatchComputeEnvironment_updateEC2 (107.14s)
--- PASS: TestAccBatchComputeEnvironment_ComputeResources_maxVCPUs (69.31s)
--- PASS: TestAccBatchComputeEnvironment_updateServiceRole (64.83s)
--- PASS: TestAccBatchComputeEnvironment_ComputeResources_minVCPUs (201.94s)
--- FAIL: TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags (284.80s)
--- PASS: TestAccBatchComputeEnvironment_createSpot (472.97s)
--- PASS: TestAccBatchComputeEnvironment_eksConfiguration (713.40s)
FAIL
FAIL github.com/hashicorp/terraform-provider-aws/internal/service/batch 716.838s
Failed test is unrelated to these changes and transient, passing after re-running:
% make testacc PKG=batch TESTS=TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/batch/... -v -count 1 -parallel 20 -run='TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags' -timeout 360m
=== RUN TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags
=== PAUSE TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags
=== CONT TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags
--- PASS: TestAccBatchComputeEnvironment_CreateEC2DesiredVCPUsEC2KeyPairImageID_computeResourcesTags (65.30s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/batch 68.466s
Thanks for your contribution, @drewmullen! 👍 |
This functionality has been released in v5.32.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Closes: #32927, #34145
Resource
Data Source