E2E: remove invalid HCLv1 field on submissions test

HCLv1 support was removed entirely in #23912, but I missed this one test and documentation reference.
hashicorp · Sep 9, 2024 · b6e7f92 · b6e7f92
1 parent cbc27e2
commit b6e7f92
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 3 deletions.
diff --git a/e2e/jobsubmissions/jobsubapi_test.go b/e2e/jobsubmissions/jobsubapi_test.go
@@ -43,7 +43,6 @@ func testParseAPI(t *testing.T) {
 
 	job, err := nomad.Jobs().ParseHCLOpts(&api.JobsParseRequest{
 		JobHCL:       string(spec),
-		HCLv1:        false,
 		Variables:    "X=\"baz\" \n Y=50 \n Z=true \n",
 		Canonicalize: true,
 	})

diff --git a/website/content/api-docs/jobs.mdx b/website/content/api-docs/jobs.mdx
@@ -243,8 +243,6 @@ The table below shows this endpoint's support for
 - `Variables` `(string: "")` - Specifies HCL2 variables to use during parsing of
   the job in the var file format.
 
-- `HCLv1` `(bool: false)` - Use the legacy v1 HCL parser.
-
 ### Sample Payload
 
 ```json