* chore(deps): bump google.golang.org/grpc from 1.69.4 to 1.71.0
* chore(deps): bump github.com/hashicorp/go-memdb from 1.3.4 to 1.3.5
* chore(deps): bump github.com/prometheus/common from 0.62.0 to 0.63.0
* chore(deps): bump github.com/hashicorp/go-kms-wrapping/wrappers/gcpckms/v2
* First batch of x-icon to hds::icons
* Bunch more icons and a note for jobrow
* Fixes for tests that depended on specific action names
* Icon-bumped-down specified to solo-icons in table cells
* Class-basing the icon bump and deferring icon svg load in env
* Exec window sidebar icons were looking a little off
* An option to select, and column etc. to view, sentinel policy scope
* Flake potential: Seed(1) had a couple jobs with the same ModifyIndex
* More de-flaking
If multiple dynamic host volumes are created in quick succession, it's possible
for the server to attempt placement on a host where another volume has been
placed but not yet fingerprinted as ready. Once a `VolumeCreate` RPC returns a
response, we've already invoked the plugin successfully and written to state, so
we're just waiting on the fingerprint for scheduling purposes. Change the
placement selection so that we skip a node if it has a volume, regardless of
whether that volume is ready yet.
Prerelease builds are in a different Artifactory repository than release
builds. Make this a variable option so we can test prerelease builds in the
nightly/weekly runs.
if the auth-url api is getting DOS'd,
then we do not expect it to still function;
we only protect the rest of the system.
users will need to use a break-glass ACL
token if they need Nomad UI/API access
during such a denial of service.
* docs: fix missing api version on acl auth method path
* docs: fix missing api version on acl binding rules path
* docs: fix missing api version on acl policies path
* docs: fix missing api version on acl roles path
* docs: fix missing api version on acl tokens path
Errors from `volume create` or `volume delete` only get logged by the client
agent, which may make it harder for volume authors to debug these tasks if they
are not also the cluster administrator with access to host logs.
Allow plugins to include an optional error message in their response. Because we
can't count on receiving this response (the error could come before the plugin
executes), we parse this message optimistically and include it only if
available.
Ref: https://hashicorp.atlassian.net/browse/NET-12087
