Closed JuicyASen closed 17 hours ago
Maybe I shouldn't test it with our org env, lol.
→ Resource Changes: 8 to create, 0 to update, 0 to re-create, 0 to delete.
module.oidc_provider.aws_iam_openid_connect_provider.github
module.terraform_locks["access-control"].aws_dynamodb_table.terraform_locks
module.terraform_roles["access-control"].aws_iam_role.remote_sts_role
module.terraform_roles["access-control"].aws_iam_role_policy_attachments_exclusive.example
module.terraform_state["access-control"].aws_s3_bucket.terraform_state
module.terraform_state["access-control"].aws_s3_bucket_public_access_block.terraform_state
module.terraform_state["access-control"].aws_s3_bucket_server_side_encryption_configuration.terraform_state
module.terraform_state["access-control"].aws_s3_bucket_versioning.terraform_state
Triggered by @JuicyASen, Commit: 86f4ccc9aae9615517da7af088094d160aa528c6
Summary
This is the initialisation of CI workflow for terraform bootstrap. Current workflow only contain terraform setup and plan. We need further discussion about the deploy strategy(
terraform apply
).Details
.github/actions/setup_with_key/action.yml
for terraform setup and initterraform init
with backend config injection.github/workflows/terraform-plan.yml
for terraform plan and print result to PRsetup_with_key
mentioned aboveterraform plan
Testing
I have tested the pipeline locally using act, with secrets managed in local files.