This pull request was automerged via backport-assistant

Signed-off-by: Grant Griffiths <ggriffiths@purestorage.com>
Co-authored-by: Grant Griffiths <ggriffiths@purestorage.com>

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

Co-authored-by: Derek Strickland <1111455+DerekStrickland@users.noreply.github.com>

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

* Capture token secret on fetch

* Fix tests

* Fix lint errors
Co-authored-by: Georges-Etienne Legendre <georges-etienne.legendre@bell.ca>

Co-authored-by: Radek Simko <radek.simko@gmail.com>

This pull request was automerged via backport-assistant

Backport of core: reschedule evicted batch job when resources become available into release/1.1.x

This PR fixes a bug where an evicted batch job would not be rescheduled
once resources become available.

Closes #9890

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

Fix numerous go-getter security issues:

- Add timeouts to http, git, and hg operations to prevent DoS
- Add size limit to http to prevent resource exhaustion
- Disable following symlinks in both artifacts and `job run`
- Stop performing initial HEAD request to avoid file corruption on
  retries and DoS opportunities.

**Approach**

Since Nomad has no ability to differentiate a DoS-via-large-artifact vs
a legitimate workload, all of the new limits are configurable at the
client agent level.

The max size of HTTP downloads is also exposed as a node attribute so
that if some workloads have large artifacts they can specify a high
limit in their jobspecs.

In the future all of this plumbing could be extended to enable/disable
specific getters or artifact downloading entirely on a per-node basis.

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

* docs: update json jobs docs

Did you know that Nomad has not 1 but 2 JSON formats for jobs? 2½ if you
want to acknowledge that sometimes our JSON job representations have a
Job top-level wrapper and sometimes do not.

The 2½ formats are:
```
 1.   HCL JSON
 2.   Input API JSON (top-level Job field)
 2.5. Output API JSON (lacks top-level Job field)
```

`#2` is what our docs consider our API JSON. `#2.5` seems to be an
accident of history we can't fix with breaking API compatibility.

`#1` is an even more interesting accident of history: the `jobspec2`
package automatically detects if the input to Parse is JSON and switches
to a JSON parser. This behavior is undocumented, the format is
unspecified, and there is no official HashiCorp tooling to produce this
JSON from HCL. The plot thickens when you discover popular third party
tools like hcl2json.com and https://github.com/tmccombs/hcl2json seem to
produce JSON that `nomad run` accepts!

Since we have no telemetry around whether or not anyone passes HCL JSON
to `nomad run`, and people don't file bugs around features that Just
Work, I'm choosing to leave that code path in place and *acknowledged
but not suggested* in documentation.

See https://github.com/hashicorp/hcl/issues/498

 for a more comprehensive
discussion of what officially supporting HCL JSON in Nomad would look
like.

(I also added some of the missing fields to the (Input API flavor) JSON
Job documentation, but it still needs a lot of work to be
comprehensive.)
Co-authored-by: Tim Gross <tgross@hashicorp.com>
Co-authored-by: temp <temp@hashicorp.com>
Co-authored-by: Tim Gross <tgross@hashicorp.com>

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

This pull request was automerged via backport-assistant

add service acct to codeowners for backport merging

During the release there are several files that need to be modified:

  - .release/ci.hcl: the notification channel needs to be updated to a
    channel with greater team visibility during the release.
  - version/version.go: the Version and VersionPrerelease variables
    need to be set so they match the release version.

After the release these files need to be reverted.

For GA releases the following additional changes also need to happen:

  - version/version.go: the Version variable needs to be bumped to the
    next version number.
  - GNUMakefile: the LAST_RELEASE variable needs to be set to the
    version that was just released.

Since the release process will commit file changes to the branch being
used for the release, it should _never_ run on main, so the first step
is now to protect against that.

It also adds a validation to make the user input version is correct.

After looking at the different release options and steps I noticed that
automatic CHANGELOG generation is actually the exception, so it would be
better to have the default to be false.

* remove website source code and related circle jobs

* remove data files

* updates platform-cli

* update local instructions

* updates package-lock