https://github.com/glueops/packer-cloud-developer-environments
https://github.com/glueops/packer-cloud-developer-environments
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/glueops/packer-cloud-developer-environments
- Owner: GlueOps
- Created: 2023-11-13T00:43:43.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-01-06T01:45:36.000Z (over 1 year ago)
- Last Synced: 2025-03-28T11:44:04.801Z (over 1 year ago)
- Language: Shell
- Size: 76.2 KB
- Stars: 0
- Watchers: 4
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# packer-cloud-developer-environments
When working locally set the following:
```bash
export PACKER_LOG=1
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export PACKER_LOG=1
export PKR_VAR_aws_access_key=$AWS_ACCESS_KEY_ID
export PKR_VAR_aws_secret_key=$AWS_SECRET_ACCESS_KEY
export PKR_VAR_glueops_codespaces_container_tag=local-dev
packer build aws.pkr.hcl
```
The packer template expects you to always do you build in us-west-2 and replicate from there to other regions.
By default the AMI will be prefixed with the date and then the codespace version. The tags for this repo should be respective of changes in this repo and not the codespaces version being used. That being said we might be using v0.30.0 of codespace and this repo could be tagged as v0.1.0 or even v0.2.0. As bug fixes are made in this repo, it will likely move at different cadence than the codespace container tag