kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-09 11:55:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9501 from hashicorp/docs-hcl-note

Browse Source 
added some discussion of HCL parsing context
This commit is contained in:
Chris Baker
2020-12-02 17:00:24 -06:00
committed by GitHub
parent dc2bec7f45 0e13770397
commit ee7c97fe91
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
website/pages/docs/job-specification/hcl2/index.mdx
View File

@@ -29,6 +29,19 @@ a quick try to HCL2, you can also read the quicker [HCL2 getting started
guide](/guides/hcl).
--->
## HCL Parsing Context
The [Nomad API uses JSON][jobs-api], not HCL, to represent Nomad jobs.
When running commands like `nomad job run` and `nomad job plan`, the Nomad CLI
parses HCL and ultimately converts it to JSON. Because this parsing happens locally
(i.e., where the operator is running the CLI) before job submission, there are some
limits to the capabilities that can be accessed by HCL job specifications. For
example, scheduling information is not yet available, including information about
the client. Similarly, HCL features that depend on external context will take that
context from the local environment of the CLI (e.g., files, environment variables).
[jobs-api]: /api-docs/jobs
## Syntax
The main purpose of the HCL language in Nomad is defining jobs. All other