Updated code to use S3 bucket name and AWS region from GitHub secrets

[hadagalikarthik]

New changes:

1. Added GitHub secrets for AWS_S3_BUCKET_NAME and AWS_REGION and declared them as environment variables in workflow file
   TF_VAR_AWS_S3_BUCKET_NAME: ${{ secrets.TF_VAR_AWS_S3_BUCKET_NAME }}
   TF_VAR_AWS_REGION: ${{ secrets.TF_VAR_AWS_REGION }}

2. Initialized backend code for those variables in workflow file under jobs wherever required, instead of declaring them in backend.tf to remove redunduncy

• name: Terraform Init
  run: |
  terraform init
  -backend-config="bucket=${{ secrets.TF_VAR_AWS_S3_BUCKET_NAME }}"
  -backend-config="region=${{ secrets.TF_VAR_AWS_REGION }}"

3. Defined AWS_REGION and AWS_S3_BUCKET_NAME in variables.tf under folders wherever required

4. Updated "bucket" and "region" variables in data.tf to use values declared in GitHub secrets

config = {
bucket = var.AWS_S3_BUCKET_NAME # Your S3 bucket name
region = var.AWS_REGION # AWS region
}

5. Replaced "tf_state_bucket" variable with "AWS_S3_BUCKET_NAME" and "aws_region" with "AWS_REGION" in S3 folder

6. Updated variable "azs" with "local.azs" and made it dynamic to build the AZ list based on region in "infra" folder
   Note :- We might need to add a note in our readme highlighting users need to use region where atleast two availability zones are supported

7. Replaced "var.azs" with "local.azs" in outputs.tf and network.tf under "infra" folder

8. "aws_region" and "azs" are no longer needed to be declared in infra->terraform.tfvars

9. Commented out "unique_bucket_name" variable, since we cannot use this in other references once we start using S3 bucket name from GitHub secrets

Please refer below pipelines for more information.
Deploy -> https://github.com/hadagalikarthik/nginx_automation_examples/actions/runs/14154048262
Destroy -> https://github.com/hadagalikarthik/nginx_automation_examples/actions/runs/14154356076

Below attached screenshot of my GitHub secrets.