docs: Migrate link formats (#2777)
* Adding docs-content-check-legacy-links-format workflow * Adding test-link-rewrites workflow * Migrating links to new format
This commit is contained in:
1 parent
87b09d5e27
commit
e6be6431b2
87 files changed
+485
-452
No files matched your search
@@ -23,12 +23,12 @@ Below is the typical structure for most Boundary CLI commands:
|
||||
boundary <command> <subcommand> [options] [args]
|
||||
```
|
||||
|
||||
- `options` - [Client](/docs/api-clients/cli#client-options) and [connection](/docs/api-clients/cli#connection-options) options to specify additional settings
|
||||
- `options` - [Client](/boundary/docs/api-clients/cli#client-options) and [connection](/boundary/docs/api-clients/cli#connection-options) options to specify additional settings
|
||||
- `args` - API arguments specific to the operation
|
||||
|
||||
#### Examples:
|
||||
|
||||
The following shows use of the [`-addr`](/docs/api-clients/cli#addr) flag to specify which Boundary controller to send the request to.
|
||||
The following shows use of the [`-addr`](/boundary/docs/api-clients/cli#addr) flag to specify which Boundary controller to send the request to.
|
||||
|
||||
```shell-session
|
||||
$ boundary authenticate password \
|
||||
|
||||
Reference in new issue
Block a user