[BUG] - AWS CI/CD deployment may fail due to S3 ACL changes

[sblair-metrostar]

Describe the bug

Due to changes made by AWS several months ago regarding S3 ACL's, I've observed deployment pipelines in both Github Actions and Gitlab failing regularly on the initial terraform state bucket stage. I've tried bypassing this with the --skip-remote-state-provision switch but this appears to not be working in the develop/extensions baseline.

Expected behavior

1. The 01-terraform-state stage should work in AWS
2. The --skip-remote-state-provision should allow bypassing of this stage

OS and architecture in which you are running Nebari

Ubuntu Linux, x64

How to Reproduce the problem?

1. Run nebari deploy... in Github Actions or Gitlab targeting an AWS environment

Command output

No response

Versions and dependencies used.

Kubernetes: 1.24
Nebari: 2023.7.2.dev

Compute environment

AWS

Integrations

No response

Anything else?

No response

[sblair-metrostar]

The fix for this was merged with PR 1915, should be able to close this issue.