Upgrade pulumi-aws provider from v6 to v7 across all infrastructure projects

[pulumi]

Summary

Upgrades pulumi-aws from v6 to v7 across all four infrastructure projects (app, backend, domain, interface). Also pins pulumi-awsx and pulumi-random explicitly where used.

Changes

requirements.txt (all 4 projects)

• pulumi-aws: >=6.0.2,<7.0.0 -> >=7.0.0,<8.0.0
• Added explicit pulumi-awsx>=3.0.0,<4.0.0 pin (app, backend, interface)
• Added explicit pulumi-random>=4.0.0,<5.0.0 pin (backend)

Code fixes for v7 compatibility

backend/main.py

• Changed engine=cluster.engine (Output[str]) to engine=aws.rds.EngineType.AURORA_POSTGRESQL to satisfy stricter v7 enum typing on ClusterInstance

app/main.py & interface/main.py

• Switched aws.ec2.get_vpc() to aws.ec2.get_vpc_output() to properly handle Output-typed arguments from stack references
• Switched aws.secretsmanager.get_secret_version() to aws.secretsmanager.get_secret_version_output() for the same reason

domain/main.py

• Updated create_records type annotation from list[CertificateDomainValidationOptionArgs] to Sequence[CertificateDomainValidationOption] to match the v7 output type from .apply()
• Added null-safety checks for optional resource_record_value and resource_record_type fields

Deployment notes

Per the v7 migration guide, the first deployment after upgrading should use pulumi up --refresh --run-program to migrate state to be compatible with the new major version.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud