one to one mapping of job-queue and computing environment

[Shiva7071007]

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

• Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

in this registry, each job queue is mapped to each computing environment. what if I want one-to-one mapping of job queue and compute env like high_priority_job_queue -> farget_compute_env low_priority_job_queue -> farget_spot_compute_env

Describe the solution you'd like.

example covering the above case, or a small change that I can do in module for personal use

Describe alternatives you've considered.

NA

Additional context

NA

[iamcgn]

I think you can solve this by just creating 2 separate modules in your own terraform. You'd have to duplicate job definitions if those are common for you but that's not the end of the world. I put this module in it's own module in my project and set up variables to create the 2 separate queues and compute environments for me. If that doesn't work for you, this is just a convenience module. You can always just create the same resources individually. It's a little more work but, honestly, not a ton.

[Shiva7071007]

I think you can solve this by just creating 2 separate modules in your own terraform. You'd have to duplicate job definitions if those are common for you but that's not the end of the world. I put this module in it's own module in my project and set up variables to create the 2 separate queues and compute environments for me. If that doesn't work for you, this is just a convenience module. You can always just create the same resources individually. It's a little more work but, honestly, not a ton.

Yup, I took reference from your module and created two modules for my use case.

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

[github-actions[bot]]

This issue was automatically closed because of stale in 10 days

[github-actions[bot]]

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.