NonOverridableArguments are not set correctly in GovCloud

[breathingdust]

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

Terraform CLI and Terraform AWS Provider Version

Affected Resource(s)

• aws_glue_job

Terraform Configuration Files

resource "aws_glue_job" "test" {
  max_capacity = 10
  name         = "%s"
  role_arn     = aws_iam_role.test.arn

  command {
    script_location = "testscriptlocation"
  }

  non_overridable_arguments = {
    "--job-bookmark-option" = "%s"
    "--job-language"        = "%s"
  }

  depends_on = [aws_iam_role_policy_attachment.test]
}

Test Output

=== CONT  TestAccAWSGlueJob_nonOverridableArguments
    resource_aws_glue_job_test.go:174: Check 2/4 error: aws_glue_job.test: Attribute 'non_overridable_arguments.%' expected "2", got "0"

Steps to Reproduce

1. make testacc TEST=./aws/ TESTARGS='-run=TestAccAWSGlueJob_nonOverridableArguments'

Important Factoids

#14793 adds support for NonOverridableArguments on aws_glue_job. In GovCloud this fails though the API's are stated to be identical between the regions.

Investigate to confirm that this is an API discrepancy, and if so file a support case with AWS.

References

Relates #14794

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions]

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.