A new platform for documentation and tutorials is launching soon.
We are migrating Hashicorp documentation into HashiCorp Developer, our new developer experience.
There are a number of options for formatting the URL provided to the
source attribute on
module blocks. This flexibility
should solve most use cases and allow for reusable policies and modules.
NOTE: All protocols are supported on the CLI, however each production Sentinel integration may not. Be sure to read the appropriate integration documentation to check the supported protocols.
- Local filesystem
- Amazon S3
- Google GCP
Due to the ambiguous nature of URLs, it is possible to force a particular protocol to be used during the fetch. To achieve this, simply prefix the url with the appropriate protocol as listed below:
The above would download the provided HTTP URL using the Git protocol.
In addition to some global options, there are options available to specific protocols to perform features such as authentication.
»Subdirectories / File Pathing
When supplying URLs that point to a directory (eg.
git), a subdirectory and
file can be provided by suffixing the URL with
// and the path. For example,
if we have a git repository that has a policy,
main.sentinel in the root, we
could directly fetch the file by using the following:
Or, if the file was nested in the
For downloads of any protocol, you can automatically verify a checksum. To
checksum a file, append a
checksum query parameter to the URL. The parameter
value can be in the format of type:value or just value, where type is "md5",
"sha1", "sha256", "sha512" or "file" . The "value" should be the actual
checksum value or download URL for "file". When type part is omitted, type will
be guessed based on the length of the checksum string.
./foo.sentinel?checksum=md5:b7d96c89d09d9e204f5fedc4d5d55b21 ./foo.sentinel?checksum=b7d96c89d09d9e204f5fedc4d5d55b21 ./foo.sentinel?checksum=file:./foo.txt.sha256sum
archive query parameter can be supplied to explicitly state what format
to attempt to extract, if required. The supported formats are:
If a URL has an extension that matches one of the supported formats, it will use that format to unarchive.
The above would use the
zip format to unarchive.
Would force the
zip format. If for some reason you required archiving to be
disabled, this can also be achieved by using the
ref- The Git ref to checkout. This is a ref, so it can point to a commit SHA, a branch name, etc. If it is a named ref such as a branch name, it will be updated to the latest on each get.
sshkey- An SSH private key to use during clones. The provided key must be a base64-encoded string. For example, to generate a suitable sshkey from a private key file on disk, you would run base64 -w0 \<file>. Note: Git 2.3+ is required to use this feature.
depth- The Git clone depth. The provided number specifies the last
nrevisions to clone from the repository.
The git getter accepts both URL-style SSH addresses like
git::ssh://firstname.lastname@example.org/foo/bar, and "scp-style" addresses like
git::email@example.com/foo/bar. In the latter case, omitting the
prefix is allowed if the username prefix is exactly git@.
The "scp-style" addresses cannot be used in conjunction with the
scheme prefix, because in that case the colon is used to mark an optional port
number to connect on, rather than to delimit the path from the host.
rev- The Mercurial revision to checkout.
To use HTTP basic authentication, simply prepend
username:password@ to the
hostname in the URL such as
All special characters, including the username and password, must be URL
The following query parameters are available and will take priority when authenticating against an S3 bucket.