mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
b09c1146a9
Several commands that inspect objects where the names are user-controlled share a bug where the user cannot inspect the object if it has a name that is an exact prefix of the name of another object (in the same namespace, where applicable). For example, the object "test" can't be inspected if there's an object with the name "testing". Copy existing logic we have for jobs, node pools, etc. to the impacted commands: * `plugin status` * `quota inspect` * `quota status` * `scaling policy info` * `service info` * `volume deregister` * `volume detach` * `volume status` If we get multiple objects for the prefix query, we check if any of them are an exact match and use that object instead of returning an error. Where possible because the prefix query signatures are the same, use a generic function that can be shared across multiple commands. Fixes: https://github.com/hashicorp/nomad/issues/13920 Fixes: https://github.com/hashicorp/nomad/issues/17132 Fixes: https://github.com/hashicorp/nomad/issues/23236 Ref: https://hashicorp.atlassian.net/browse/NET-10054 Ref: https://hashicorp.atlassian.net/browse/NET-10055
20 lines
799 B
Plaintext
20 lines
799 B
Plaintext
```release-note:bug
|
|
cli: Fixed bug where the `plugin status` command would fail if the plugin ID was a prefix of another plugin ID
|
|
```
|
|
|
|
```release-note:bug
|
|
cli: Fixed bug where the `quota status` and `quota inspect` commands would fail if the quota name was a prefix of another quota name
|
|
```
|
|
|
|
```release-note:bug
|
|
cli: Fixed bug where the `scaling policy info` command would fail if the policy ID was a prefix of another policy ID
|
|
```
|
|
|
|
```release-note:bug
|
|
cli: Fixed bug where the `service info` command would fail if the service name was a prefix of another service name in the same namespace
|
|
```
|
|
|
|
```release-note:bug
|
|
cli: Fixed bug where the `volume deregister`, `volume detach`, and `volume status` commands would fail if the volume ID was a prefix of another volume ID in the same namespace
|
|
```
|