drudgesentinel/stotem: Basic tool for helping with setup of local environments for troubleshooting Hashicorp Sentinel

Basic tool for helping with setup of local environments for troubleshooting Hashicorp Sentinel

Go to file

Sean Meininger ed7a5afef7 add writing tests to to-do list		2022-10-09 21:33:41 -07:00
src	fixed dependencies for main	2022-10-09 21:30:21 -07:00
.gitignore	third initial commit	2022-10-07 17:29:45 -07:00
package-lock.json	fixed dependencies for main	2022-10-09 21:30:21 -07:00
package.json	fixed dependencies for main	2022-10-09 21:30:21 -07:00
README.md	add writing tests to to-do list	2022-10-09 21:33:41 -07:00
tsconfig.json	third initial commit	2022-10-07 17:29:45 -07:00

README.md

This tool aims to simplify setting up local reproduction environments for writing and testing Sentinel policies.

At present, navigate to your sentinel policy directory (containing the .hcl) and run main.js there.

Current functionality: Checks the CURRENT DIRECTORY recursively(via vsCode's ripgrep package) for references to the Hashicorp governance repo common-functions and adds them as http imports to sentinel.hcl if found.

Planned functionality: WORKING TESTS Check for v1 imports and print a warning if they're in use

Provide a command line flag to show what values will be after_unknown

TBD: Considering whether an offline/local mode is worth implementing. This would work by replacing the https heredocs with local copies of repo functions included with an npm tarball (or just include it directly in this package)