Skip to content

Commit

Permalink
make gen-markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
@petersutter
petersutter committed May 25, 2023
1 parent b86044c commit 03cc506
Show file tree
Hide file tree
Showing 6 changed files with 19 additions and 13 deletions.
19 changes: 10 additions & 9 deletions docs/help/gardenctl_provider-env.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,16 @@ gardenctl provider-env [flags]
### Options

```
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Generate the script even if there are access restrictions to be confirmed
--garden string target the given garden cluster
-h, --help help for provider-env
-o, --output string One of 'yaml' or 'json'.
--project string target the given project
--seed string target the given seed cluster
--shoot string target the given shoot cluster
-u, --unset Generate the script to unset the cloud provider CLI environment variables and logout for
-y, --confirm-access-restriction Confirm any access restrictions. Set this flag only if you are completely aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Deprecated. Use --confirm-access-restriction instead. Generate the script even if there are access restrictions to be confirmed.
--garden string target the given garden cluster
-h, --help help for provider-env
-o, --output string One of 'yaml' or 'json'.
--project string target the given project
--seed string target the given seed cluster
--shoot string target the given shoot cluster
-u, --unset Generate the script to unset the cloud provider CLI environment variables and logout for
```

### Options inherited from parent commands
Expand Down
3 changes: 2 additions & 1 deletion docs/help/gardenctl_provider-env_bash.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ gardenctl provider-env bash [flags]
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--config string config file (default is ~/.garden/gardenctl-v2.yaml)
-y, --confirm-access-restriction Confirm any access restrictions. Set this flag only if you are completely aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Generate the script even if there are access restrictions to be confirmed
-f, --force Deprecated. Use --confirm-access-restriction instead. Generate the script even if there are access restrictions to be confirmed.
--garden string target the given garden cluster
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
Expand Down
3 changes: 2 additions & 1 deletion docs/help/gardenctl_provider-env_fish.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ gardenctl provider-env fish [flags]
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--config string config file (default is ~/.garden/gardenctl-v2.yaml)
-y, --confirm-access-restriction Confirm any access restrictions. Set this flag only if you are completely aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Generate the script even if there are access restrictions to be confirmed
-f, --force Deprecated. Use --confirm-access-restriction instead. Generate the script even if there are access restrictions to be confirmed.
--garden string target the given garden cluster
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
Expand Down
3 changes: 2 additions & 1 deletion docs/help/gardenctl_provider-env_powershell.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ gardenctl provider-env powershell [flags]
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--config string config file (default is ~/.garden/gardenctl-v2.yaml)
-y, --confirm-access-restriction Confirm any access restrictions. Set this flag only if you are completely aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Generate the script even if there are access restrictions to be confirmed
-f, --force Deprecated. Use --confirm-access-restriction instead. Generate the script even if there are access restrictions to be confirmed.
--garden string target the given garden cluster
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
Expand Down
3 changes: 2 additions & 1 deletion docs/help/gardenctl_provider-env_zsh.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,9 @@ gardenctl provider-env zsh [flags]
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--config string config file (default is ~/.garden/gardenctl-v2.yaml)
-y, --confirm-access-restriction Confirm any access restrictions. Set this flag only if you are completely aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
-f, --force Generate the script even if there are access restrictions to be confirmed
-f, --force Deprecated. Use --confirm-access-restriction instead. Generate the script even if there are access restrictions to be confirmed.
--garden string target the given garden cluster
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
Expand Down
1 change: 1 addition & 0 deletions docs/help/gardenctl_ssh.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,7 @@ gardenctl ssh --keep-bastion --bastion-name cli-xxxxxxxx --public-key-file /path
--bastion-port string SSH port of the bastion used for the SSH client command. Defaults to port 22 (default "22")
--bastion-user-known-hosts-file strings Path to a custom known hosts file for the SSH connection to the bastion. This file is used to verify the public keys of remote hosts when establishing a secure connection.
--cidr stringArray CIDRs to allow access to the bastion host; if not given, your system's public IPs (v4 and v6) are auto-detected.
-y, --confirm-access-restriction Bypasses the need for confirmation of any access restrictions. Set this flag only if you are fully aware of the access restrictions.
--control-plane target control plane of shoot, use together with shoot argument
--garden string target the given garden cluster
-h, --help help for ssh
Expand Down

0 comments on commit 03cc506

Please sign in to comment.