wf deploy component

wf deploy component

Deploys a single component to an application environment

Synopsis

Generates kubernetes manifests for the given component and deploys them to an application environment.

This command is equivalent to running 'wf deploy app --only component'.

Optionally opt to return the generate manifests to stdout (--dry-run) or to disk (--path) without applying them.

wf deploy component [flags]

Examples

# General usage: 
$ wf deploy component APP APPENV --component COMPONENT_NAME

For full usage, see wf help deploy app

Options

  -a, --application string        the application to deploy to
      --component string          component to deploy
      --deploy-role string        role to assume before deploying (default unless using a access token: namespace.edit)
      --dry-run                   outputs manifests for the application to stdout without applying them (default: false)
      --eject                     returns base manifests, kustomize.yaml, and patches (default: false)
  -e, --env string                the environment to deploy to
      --force                     force override in the case of ownership conflicts when patching resources on deployment (default: false)
  -h, --help                      help for component
      --image string              optional image to use to deploy (for a container component) e.g. ghcr.io/org/project/image:v1.2.3 or ghcr.io/org/project/image
      --image-tag string          optional image tag to use to deploy (for a container component) e.g. v1.2.3
      --no-role                   deploys without first assuming a deployment role (default if using a access token, unless --deploy-role specified)
      --only strings              return only the specified components from the command
  -p, --path string               the dir to output to
      --remove                    removes the objects represented by this application from the environment (default: false)
      --wait-for-ready duration   Wait for up to the supplied duration for all resources to have a ready status after applying, e.g. 30s

Options inherited from parent commands

      --debug              Indicates we should use debug / trace logging (default: false)
      --no-wait            Indicates we should not wait for resources to provision
  -o, --output string      Output format of the resource (json,yaml,table,template) (default "table")
      --profile string     Use a profile other than your default for this command
      --show-headers       Indicates we should display headers on table out (default true)
      --verbose            Enables verbose logging for debugging purposes (default: false)
  -w, --workspace string   The workspace you are operating within

SEE ALSO

• wf deploy - Deploys a resource to Wayfinder