Gardenctl Provider Env Bash

gardenctl provider-env bash

Generate the cloud provider CLI configuration script for bash

Synopsis

Generate the cloud provider CLI configuration script for bash.

To load the cloud provider CLI configuration script in your current shell session: $ eval "$(gardenctl provider-env bash)"

gardenctl provider-env bash [flags]

Options

  -h, --help   help for bash

Options inherited from parent commands

      --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                                         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)
      --log-file string                               If non-empty, use this log file (no effect when -logtostderr=true)
      --log-file-max-size uint                        Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                                   log to standard error instead of files (default true)
      --one-output                                    If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
      --openstack-allowed-patterns stringArray        Additional allowed patterns for OpenStack credential fields in JSON format.
                                                      Note: Only the 'authURL' field is supported for OpenStack pattern validation.
                                                      Each pattern should be a JSON object with fields like:
                                                      {"field": "authURL", "host": "keystone.example.com"}
                                                      {"field": "authURL", "host": "keystone.example.com", "path": "/v3"}
                                                      {"field": "authURL", "regexValue": "^https://[a-z0-9.-]+\\.example\\.com(:[0-9]+)?/.*$"}
                                                      These are merged with defaults and configuration.
      --openstack-allowed-uri-patterns strings        Simplified URI patterns for OpenStack credential fields in the format 'field=uri'.
                                                      Note: Only the 'authURL' field is supported for OpenStack pattern validation.
                                                      For example:
                                                      "authURL=https://keystone.example.com:5000/v3"
                                                      "authURL=https://keystone.example.com/identity/v3"
                                                      The URI is parsed and host and path are set accordingly. These are merged with defaults and configuration.
      --project string                                target the given project
      --seed string                                   target the given seed cluster
      --shoot string                                  target the given shoot cluster
      --skip-headers                                  If true, avoid header prefixes in the log messages
      --skip-log-headers                              If true, avoid headers when opening log files (no effect when -logtostderr=true)
      --stackit-allowed-patterns stringArray          Additional allowed patterns for STACKIT credential fields in JSON format.
                                                      Note: Only the 'aud' field in the serviceaccount under credentials is supported for STACKIT pattern validation.
                                                      Each pattern should be a JSON object with fields like:
                                                      {"field": "aud", "host": "https://example.com"}
                                                      {"field": "aud", "regexValue": "^https://[a-z0-9.-]+\\.example\\.com(:[0-9]+)?/.*$"}
                                                      These are merged with defaults and configuration.
      --stackit-allowed-uri-patterns strings          Simplified URI patterns for STACKIT credential fields in the format 'field=uri'.
                                                      Note: Only the 'aud' field in the serviceaccount under credentials is supported for STACKIT pattern validation.
                                                      For example:
                                                      "aud=https://example.com"
                                                      The URI is parsed and host and path are set accordingly. These are merged with defaults and configuration.
      --stderrthreshold severity                      logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)
  -u, --unset                                         Generate the script to unset the cloud provider CLI environment variables and logout.
  -v, --v Level                                       number for the log level verbosity
      --vmodule moduleSpec                            comma-separated list of pattern=N settings for file-filtered logging
      --workload-identity-token-expiration duration   Requested expiration for workload identity tokens. The server may enforce a maximum. (default 1h0m0s)

SEE ALSO

• gardenctl provider-env - Generate the cloud provider CLI configuration script for the specified shell