mirror of
https://github.com/hashicorp/action-setup-enos
synced 2026-04-05 19:04:25 +00:00
No description
- JavaScript 100%
It appears that our usage of @action/http-client transitively "depends" (from what I can see, it's not actually used and probably ought to be a dev dependency in the http-client module) on undici 6.23.0[0]. The upstream hasn't been updated yet so we add an override for it here. Since we're doing a security release I also updated all of our outdated deps. [0]: https://github.com/actions/toolkit/blob/main/packages/http-client/package-lock.json#L235 Signed-off-by: Ryan Cragun <me@ryan.ec> |
||
|---|---|---|
| .github | ||
| __tests__ | ||
| dist | ||
| src | ||
| .copywrite.hcl | ||
| .gitignore | ||
| .prettierignore | ||
| action.yml | ||
| eslint.config.js | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vitest.config.mjs | ||
action-setup-enos
action-setup-enos downloads and installs the enos CLI into
the runner environment.
Many enos CLI sub-commands require the terraform binary to be in the default PATH. You can
install Terraform on the runner using the setup-terraform.
Important
Use
setup-terraform@v3or later, otherwise you'll need to setterraform-wrapper: falseas the wrapper in prior versions will break theenosCLI's ability to executeterraformcorrectly.
Usage
steps:
- name: Set up Terraform
uses: hashicorp/setup-terraform@v3
- name: Set up Enos
uses: hashicorp/action-setup-enos@v1
with:
version: 0.0.36 # You only need to specify a version if you wish to override the default version
Inputs
The actions supports the following inputs:
version: The version ofenosto install, defaulting to0.0.36
Release a new version of Enos
- Ensure that you have the latest version of Node 24 (krypton) installed
- Ensure that you have installed the copywrite utility for writing copywrite headers.
- Bump the version in
package.json. This is the action version, not the enos cli version, it wont likely match the enos version - If we're releasing a new version of
enos:- Change the
latestVersioninsrc/enos.jsto reflect the new version. - Update references to specific version in the
README.mdto the new version.
- Change the
- Run
npm i && npm run allto compile, format, add license headers, lint, and test the action. - If all of the npm scripts pass then create a PR with the modified files.
- Get review and the PR merged
After the pull request is merged it will automatically be released with the tagrelease Github Actions workflow.
Note
If for some reason you need to manually update the
v1tag you can do so with:
TAG="v$(cat package.json| jq -r '.version')"
git tag -a -m "$TAG" $TAG
git tag -a -m "$TAG" v1 -f
git push --tags -f