Skip to content

Conversation

@ibisio-gocloud
Copy link

@ibisio-gocloud ibisio-gocloud commented Jun 23, 2025

Description

Updated aws_batch_job_queue resource to use the new compute_environment_order block format introduced in newer versions of the AWS provider. This replaces the deprecated compute_environments list attribute. Additionally, aligned naming attributes in aws_batch_compute_environment to the latest supported name and name_prefix syntax from AWS provider 6.0.

Motivation and Context

This change is required to maintain compatibility with recent versions of the AWS provider 6.0, which deprecated the compute_environments attribute in aws_batch_job_queue in favor of explicit compute_environment_order blocks. Also addresses the renaming of compute_environment_name to name and compute_environment_name_prefix to name_prefix in aws_batch_compute_environment.

Reference: AWS Provider v6.0.0 Changelog

Breaking Changes

No breaking changes.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@vampirechicken
Copy link

AWS provider 5.40.0 removes the deprecated the compute_environments variable on March 7, 2024. Provider 6.0.0 - released June 18 2025 - removes it in favor of compute_environment_order.

This is an important PR for module users.

Copy link
Member

@bryantbiggs bryantbiggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the change as it stands is not valid - there are other breaking changes that will be made in the same change set including changes to handle the deprecated arguments that have been removed

@ibisio-gocloud
Copy link
Author

the change as it stands is not valid - there are other breaking changes that will be made in the same change set including changes to handle the deprecated arguments that have been removed

Understood, I will add the other changes that are included in the other PR along with the other changes that were made in version 5.X of the provider

@antonbabenko
Copy link
Member

This issue has been resolved in version 3.0.0 🎉

@github-actions
Copy link

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. If you have found a problem that seems related to this change, 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 Jul 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants