• Expose service role, so that it can be used as input for other modules.
• Fix terratest tests for environment creation.

why

• It can be leveraged in conjunction of the Elastic Beanstalk Application. Since the service role is already created by the EB environment module.
• Fixing Terratest allows reliable automated validation of this module.

references

• For instance, it can be referred in in the module Elastic Beanstalk Application appversion_lifecycle_service_role_arn as part of lifecycle role cleanup
• Terratest error while testing:
  Error: creating Elastic Beanstalk Environment (eg-test-eb-env-shared-alb-qjkk0y): operation error Elastic Beanstalk: CreateEnvironment, https response error StatusCode: 400, RequestID: f6b66297-8b0d-4902-a3d8-934ffc0c4a32, api error InvalidParameterValue: No Solution Stack named '64bit Amazon Linux 2023 v4.0.1 running Python 3.11'

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• golang/go#59305 (comment)
• cloudposse/terraform-aws-cloudfront-s3-cdn#294

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub