https://github.com/softwareag/sag-devcontainer-aws-terraform-template-01
Template showing how to start developing with Terraform and the given devcontainer
https://github.com/softwareag/sag-devcontainer-aws-terraform-template-01
Last synced: about 1 year ago
JSON representation
Template showing how to start developing with Terraform and the given devcontainer
- Host: GitHub
- URL: https://github.com/softwareag/sag-devcontainer-aws-terraform-template-01
- Owner: SoftwareAG
- License: apache-2.0
- Created: 2024-01-10T10:00:49.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-05-06T13:46:11.000Z (about 2 years ago)
- Last Synced: 2025-02-13T09:29:44.530Z (over 1 year ago)
- Language: HCL
- Size: 15.6 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Template showing how to start developing with Terraform and the given devcontainer
The purpose of this template is to allow for a quick start with AWS IaC projects using the provided devcontainer.
## Quick Start
- ensure the prerequisites:
- Development box (PC, remote dev machine etc.):
- PC able to run docker compose projects
- git client(s) to clone the repository
- Visual Studio Code
- AWS
- account where permissions do administer resources is granted
- generate a new repository from the template
- clone the generated repository
- open the folder in Visual Studio Code
- the IDE detects the presence of a devcontainer and asks to "reopen in container"
- once Visual Studio Code reopens in container:
- Select AWS extensions and execute the necessary log ins
- Select the checkov extension and add the API token. If you don't have one, register to the service
- Details [here](https://marketplace.visualstudio.com/items?itemName=Bridgecrew.checkov#:~:text=Open%20a%20file%20you%20wish,now%20appear%20in%20your%20editor.)
- In a terminal:
- execute `aws configure` and connect the shell to AWS
- execute `cd /workshop && terraform init`
## Other Aspects
If you want to use this template for multiple projects, it is recommended to change the submodule mount path to unique names, otherwise the docker compose operations on the same directory may go in conflict with one another. This can be easily achieved with a `git move` command as explained in [this article](https://themightyprogrammer.dev/snippet/moving-git-submodule).