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.

Sign up for GitHub

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

Jump to bottom

r/aws_batch_compute_environment: Additional attributes can be updated in-place #24374

Closed
ewbankkit opened this issue Apr 23, 2022 · 3 comments · Fixed by #30438
Closed

r/aws_batch_compute_environment: Additional attributes can be updated in-place #24374

ewbankkit opened this issue Apr 23, 2022 · 3 comments · Fixed by #30438
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/batch Issues and PRs that pertain to the batch service.
Milestone
v5.10.0

Comments

@ewbankkit
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

From the recent AWS announcement:

AWS Batch now expands the Compute environment (CE) configuration parameters that can be updated without having to recreate compute environments. Previously customers used UpdateComputeEnvironment API to change CE state, desired CPU count, min and max vCPU count, and service role. To update additional configuration parameters, customers have to create new CEs. With this launch, customers can use the UpdateComputeEnvironment API to dynamically update CE configuration parameters such as AMI, EC2 launch templates, instance types, and more. Rather than having to manually create a new CE to use the updated configurations, Batch will use the updated CE configuration while launching new instances and terminate instances using old CE configuration once the jobs running on them are completed.

New or Affected Resource(s)

References

AWS Batch User Guide.
@ewbankkit ewbankkit added enhancement Requests to existing resources that expand the functionality or scope. service/batch Issues and PRs that pertain to the batch service. labels Apr 23, 2022
@aaleksandrov aaleksandrov mentioned this issue Jun 30, 2022
Closed
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Jul 22, 2022
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
f6cee86
@sworisbreathing sworisbreathing mentioned this issue Jul 22, 2022
Closed
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Jul 22, 2022
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
7ffe678
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Jul 22, 2022
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
b3f9812
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Aug 2, 2022
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
e8b6f7b
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Aug 2, 2022
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
642c7e9 
Stop erroneously trying to update the ec2 configuration on batch environment updates when there are no changes to it
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 3, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
2b68efa 
Stop erroneously trying to update the ec2 configuration on batch environment updates when there are no changes to it
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 4, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
b853599 
Stop erroneously trying to update the ec2 configuration on batch environment updates when there are no changes to it
@sworisbreathing sworisbreathing mentioned this issue Apr 4, 2023
Merged
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 4, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
5cd2752
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 4, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
0163625
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 4, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
b8e7e04
sworisbreathing added a commit to sworisbreathing/terraform-provider-aws that referenced this issue Apr 4, 2023
@sworisbreathing
Make batch compute environments updatable. Fixes hashicorpGH-24374
1a93a42
@nicholastulach
Copy link

In the meantime, how do we work around this if we want to update our compute environments in terraform?

ewbankkit added a commit that referenced this issue Jul 25, 2023
@ewbankkit
Merge pull request #30438 from sworisbreathing/f-aws_batch_compute_en…
cc19bfd 
…vironment-make-updatable

Make batch compute environments updatable. Fixes GH-24374
@github-actions github-actions bot added this to the v5.10.0 milestone Jul 25, 2023
@github-actions
Copy link

This functionality has been released in v5.10.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!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/batch Issues and PRs that pertain to the batch service.
Projects
None yet
Milestone
v5.10.0
2 participants
@nicholastulach @ewbankkit