Skip to content

Commit

Permalink
chore: create a new s3 resource
Browse files Browse the repository at this point in the history
  • Loading branch information
rcmonteiro committed Jun 14, 2024
1 parent 3b4e557 commit 78e5c57
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 9 deletions.
1 change: 1 addition & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -46,4 +46,5 @@ jobs:
run: terraform plan

- name: Run Terraform Apply
if: github.ref == 'refs/heads/main' && github.event_name == 'push'
run: terraform apply -auto-approve
12 changes: 3 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,12 +65,6 @@ AWS_PROFILE={your_aws_profile} terraform apply -var-file="secret.tfvars"

Type `yes` to apply the changes.

Now we have deployed the App on App Runner, but, we still have work to do, to make the CD process automated.

## Deployment

```bash
terraform init
terraform plan
terraform apply
```
Now we can commit the changes to the repository, and check the logs for the pipeline.
For this example, nothing will be changed, since we have already applied the changes locally.
But If you add a new resource, like a new S3 bucket, you will see the changes in the pipeline, and they will be created in the AWS account.
7 changes: 7 additions & 0 deletions s3.tf
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
resource "aws_s3_bucket" "s3-test" {
bucket = "devops-create-image-nest-iac-new-bucket"

tags = {
IaC = "True"
}
}

0 comments on commit 78e5c57

Please sign in to comment.