fix: Remove erroneous pod_properties
scoping from job definition variable attribute structure
#45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes the way EKS pod properties are referenced in the aws_batch_job_definition resource in main.tf.
The module previously accessed attributes like dns_policy, host_network, image_pull_secrets, etc. from eks_properties.value.pod_properties, but according to the variable definition, these should be accessed directly from eks_properties.value.
Motivation and Context
This change is required to align the module implementation with the variable structure defined in variables.tf.
It solves errors like:
and similar errors for other attributes.
Breaking Changes
No breaking changes. This PR only corrects attribute references to match the documented variable structure.
How Has This Been Tested?
Used a minimal EKS job definition with pod properties and confirmed that the job definition is created successfully.
Verified that the AWS Console displays the "Pod Properties" tab and all configured properties.