Test upgrade on the abundant namespace (test namespace) and on an EKS module

[AntonyBishop]

Background

Test upgrade on the abundant namespace (test namespace) and on an EKS module.

One test each module.

Approach

TBC

Which part of the user docs does this impact

N/A

Questions / Assumptions

Definition of done

• [ ] Testing complete
• [ ] Any issues identified and resolved

Reference

How to write good user stories

[poornima-krishnasamy]

Tested modules for plan and apply with 1.2.5 on abundant-namespace-dev: aurora dynamodb elasticache elastisearch rds-postgres s3 serviceaccount sns sqs irsa

Tested Plan for dms module in hmpps-workload-preprod namespace

There are few changes to

• kubernetes_secret resource - Adds sensitive_attributes. Hence, the kubernetes_secret resources is updated when doing hte upgrade
• rds-postgres: - Adds sensitive_attributes
• rds-aurora: - Adds sensitive_attributes

Comparing the state files: Modules dependencies has been updated with data resource too

[poornima-krishnasamy]

Testing done and all modules changes to version 1.2.5