nomad-firehose icon indicating copy to clipboard operation
nomad-firehose copied to clipboard

Bump github.com/hashicorp/nomad from 0.8.6 to 0.10.4

Open dependabot-preview[bot] opened this issue 4 years ago • 3 comments

Bumps github.com/hashicorp/nomad from 0.8.6 to 0.10.4.

Release notes

Sourced from github.com/hashicorp/nomad's releases.

v0.10.4

FEATURES:

  • api: Nomad now supports ability to remotely request /debug/pprof endpoints from a remote agent. [GH-6841]
  • consul/connect: Nomad may now register Consul Connect services when Consul is configured with ACLs enabled [GH-6701]
  • jobspec: Add shutdown_delay to task groups so task groups can delay shutdown after deregistering from Consul [GH-6746]

IMPROVEMENTS:

  • Our Windows 32-bit and 64-bit executables for this version and up will be signed with a HashiCorp cert. Windows users will no longer see a warning about an "unknown publisher" when running our software.
  • build: Updated to Go 1.12.16 [GH-7009]
  • cli: Included namespace in output when querying job status [GH-6912]
  • cli: Added option to change the name of the file created by the nomad init command [GH-6520](hashicorp/nomad#6520)
  • client: Supported AWS EC2 Instance Metadata Service Version 2 (IMDSv2) [GH-6779]
  • consul: Add support for service canary_meta [GH-6690]
  • driver/docker: Added a disable_log_collection parameter to disable nomad log collection [GH-6820]
  • server: Introduced a default_scheduler_config config parameter to seed initial preemption configuration. [GH-6935]
  • scheduler: Removed penalty for allocation's previous node if the allocation did not fail. [GH-6781]
  • scheduler: Reduced logging verbosity during preemption [GH-6849]
  • ui: Updated Run Job button to be conditionally enabled according to ACLs [GH-5944]

BUG FIXES:

  • agent: Fixed a panic when using nomad monitor on a client node [GH-7053]
  • agent: Fixed race condition in logging when using nomad monitor command [GH-6872]
  • agent: Fixed a bug where nomad monitor -server-id only work for a server's name instead of uuid or name [GH-7015]
  • core: Addressed an inconsistency where allocations created prior to 0.9 had missing fields [GH-6922]
  • cli: Fixed a bug where error messages appeared interleaved with help text inconsistently [GH-6865]
  • cli: Fixed a bug where nomad monitor -node-id would cause a cli panic when no nodes where found [GH-6828]
  • config: Fixed a bug where agent startup would fail if the consul.timeout configuration was set [GH-6907]
  • consul: Fixed a bug where script-based health checks would fail if the service configuration included interpolation [GH-6916]
  • consul/connect: Fixed a bug where Connect-enabled jobs failed to validate when service names used interpolation [GH-6855]
  • drivers: Fixed a bug where exec, java, and raw_exec drivers collected and emited stats every second regardless of the telemetry config [GH-7043]
  • driver/exec: Fixed a bug where systemd cgroup wasn't removed upon a task completion [GH-6839]
  • server: Fixed a deadlock that may occur when server leadership flaps very quickly [GH-6977]
  • scheduler: Fixed a bug that caused evicted allocs on a lost node to be stuck in running [GH-6902]
  • scheduler: Fixed a bug where nomad job plan/apply returned errors instead of ignoring system job updates for ineligible nodes. [GH-6996]

SECURITY:

  • client: Nomad will no longer pass through the CONSUL_HTTP_TOKEN environment variable when launching a task. [GH-7131]

v0.10.4-rc1

FEATURES:

  • api: Nomad now supports ability to remotely request /debug/pprof endpoints from a remote agent. [GH-6841]
  • consul/connect: Nomad may now register Consul Connect services when Consul is configured with ACLs enabled [GH-6701]
  • jobspec: Add shutdown_delay to task groups so task groups can delay shutdown after deregistering from Consul [GH-6746]

IMPROVEMENTS:

... (truncated)
Changelog

Sourced from github.com/hashicorp/nomad's changelog.

0.10.4 (February 19, 2020)

FEATURES:

  • api: Nomad now supports ability to remotely request /debug/pprof endpoints from a remote agent. [GH-6841]
  • consul/connect: Nomad may now register Consul Connect services when Consul is configured with ACLs enabled [GH-6701]
  • jobspec: Add shutdown_delay to task groups so task groups can delay shutdown after deregistering from Consul [GH-6746]

IMPROVEMENTS:

  • Our Windows 32-bit and 64-bit executables for this version and up will be signed with a HashiCorp cert. Windows users will no longer see a warning about an "unknown publisher" when running our software.
  • build: Updated to Go 1.12.16 [GH-7009]
  • cli: Included namespace in output when querying job status [GH-6912]
  • cli: Added option to change the name of the file created by the nomad init command [GH-6520](hashicorp/nomad#6520)
  • client: Supported AWS EC2 Instance Metadata Service Version 2 (IMDSv2) [GH-6779]
  • consul: Add support for service canary_meta [GH-6690]
  • driver/docker: Added a disable_log_collection parameter to disable nomad log collection [GH-6820]
  • server: Introduced a default_scheduler_config config parameter to seed initial preemption configuration. [GH-6935]
  • scheduler: Removed penalty for allocation's previous node if the allocation did not fail. [GH-6781]
  • scheduler: Reduced logging verbosity during preemption [GH-6849]
  • ui: Updated Run Job button to be conditionally enabled according to ACLs [GH-5944]

BUG FIXES:

  • agent: Fixed a panic when using nomad monitor on a client node [GH-7053]
  • agent: Fixed race condition in logging when using nomad monitor command [GH-6872]
  • agent: Fixed a bug where nomad monitor -server-id only work for a server's name instead of uuid or name [GH-7015]
  • core: Addressed an inconsistency where allocations created prior to 0.9 had missing fields [GH-6922]
  • cli: Fixed a bug where error messages appeared interleaved with help text inconsistently [GH-6865]
  • cli: Fixed a bug where nomad monitor -node-id would cause a cli panic when no nodes where found [GH-6828]
  • config: Fixed a bug where agent startup would fail if the consul.timeout configuration was set [GH-6907]
  • consul: Fixed a bug where script-based health checks would fail if the service configuration included interpolation [GH-6916]
  • consul/connect: Fixed a bug where Connect-enabled jobs failed to validate when service names used interpolation [GH-6855]
  • drivers: Fixed a bug where exec, java, and raw_exec drivers collected and emited stats every second regardless of the telemetry config [GH-7043]
  • driver/exec: Fixed a bug where systemd cgroup wasn't removed upon a task completion [GH-6839]
  • server: Fixed a deadlock that may occur when server leadership flaps very quickly [GH-6977]
  • scheduler: Fixed a bug that caused evicted allocs on a lost node to be stuck in running [GH-6902]
  • scheduler: Fixed a bug where nomad job plan/apply returned errors instead of ignoring system job updates for ineligible nodes. [GH-6996]

SECURITY:

  • client: Nomad will no longer pass through the CONSUL_HTTP_TOKEN environment variable when launching a task. [GH-7131]

0.10.3 (January 29, 2020)

SECURITY:

  • agent: Added unauthenticated connection timeouts and limits to prevent resource exhaustion. CVE-2020-7218 [GH-7002]
  • server: Fixed insufficient validation for role and region for RPC connections when TLS enabled. CVE-2020-7956 [GH-7003]
... (truncated)
Commits
  • 646df47 Release v0.10.4
  • f750636 Generate files for 0.10.4 release
  • 81c73e4 release: prep 0.10.4
  • 4c4dd0f Merge pull request #7129 from hashicorp/b-consistent-ct-name
  • 0a93ddd Merge pull request #7127 from hashicorp/b-unset-ct
  • 7173cb2 docs: update changelog mentioning consul token passthrough
  • 5ccc9a6 command: use consistent CONSUL_HTTP_TOKEN name
  • b5b5e50 nomad: assert consul token is unset on job register in tests
  • a67710c nomad: unset consul token on job register
  • 76e1785 Merge pull request #7122 from hashicorp/pprof/changelog
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

dependabot-preview[bot] avatar Feb 20 '20 10:02 dependabot-preview[bot]

Dependabot tried to update this pull request, but something went wrong. The most likely cause is #141, which may be blocking Dependabot from updating your dependency files.

dependabot-preview[bot] avatar Mar 20 '20 12:03 dependabot-preview[bot]

Dependabot tried to update this pull request, but something went wrong. The most likely cause is #141, which may be blocking Dependabot from updating your dependency files.

dependabot-preview[bot] avatar Mar 20 '20 13:03 dependabot-preview[bot]

Dependabot tried to update this pull request, but something went wrong. The most likely cause is #141, which may be blocking Dependabot from updating your dependency files.

dependabot-preview[bot] avatar Sep 03 '20 16:09 dependabot-preview[bot]