You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 13, 2026. It is now read-only.
Run the deploy pipeline for pushes to branches that start with `test/`
to automate the creation of test artifacts and streamline the manual
testing process.
Pushing directly to a branch requires write permission to the repo,
restricting who can create a test artifact.
* Packer deploys a new AMI to the AWS account specified by the AwsProfile
58
73
* Subsequent builds may require the [-force](https://packer.io/docs/commands/build.html#force) flag
74
+
* Test AMIs can be built automatically by pushing directly to a branch beginning with `test/`
59
75
60
-
### Image Accessability
61
-
This project is setup to build publicly accessible images. To change it to
62
-
build private images please refer to the [packer documentation](https://packer.io/docs/builders/amazon-ebs.html)
63
-
for `ami_users` and `snapshot_users`options.
64
-
65
-
### Testing
66
-
As a pre-deployment step we syntatically validate our packer json
67
-
files with [pre-commit](https://pre-commit.com).
68
-
69
-
Please install pre-commit, once installed the file validations will
70
-
automatically run on every commit. Alternatively you can manually
71
-
execute the validations by running `pre-commit run --all-files`.
76
+
The process for testing the integration of an AMI with cloudformation init scripts
77
+
is outlined in the [`organizations-infra` docs for service catalog](https://github.com/Sage-Bionetworks-IT/organizations-infra/blob/master/sceptre/scipool/README.md)
72
78
73
79
### CI Workflow
74
80
The workflow to provision AWS AMI is done using pull requests.
0 commit comments