Skip to main content

Overview

flytectl update modifies existing Flyte resources in FlyteAdmin.
flytectl update <resource> [name] -p <project> -d <domain> [flags]

Subcommands

SubcommandDescription
update projectActivate, archive, or edit project metadata
update launchplanActivate or deactivate a launch plan schedule
update launchplan-metaUpdate a launch plan’s description or archive state
update executionUpdate execution tags or state
update task-metaUpdate a task’s description or archive state
update workflow-metaUpdate a workflow’s description or archive state
update task-resource-attributeUpdate task resource default/limit overrides
update cluster-resource-attributeUpdate cluster resource attribute overrides
update execution-cluster-labelUpdate execution cluster label overrides
update execution-queue-attributeUpdate execution queue attribute overrides
update plugin-overrideUpdate plugin override settings
update workflow-execution-configUpdate workflow execution config overrides

update project

Modify project metadata, or archive/activate a project.
# Activate (unarchive) a project
flytectl update project -p my-project-id --activate

# Archive a project
flytectl update project -p my-project-id --archive

# Update description and labels
flytectl update project -p my-project-id \
  --description "A wonderful project" \
  --labels app=my-app

# Update from a YAML file
flytectl update project --file project.yaml
Update YAML file format:
id: "my-project-id"
name: "my-project-name"
labels:
  values:
    app: my-app
description: "A wonderful project"
Archive or activate via YAML file: To archive a project using a YAML file, set state: 1 and pass --archive:
# update.yaml
id: "my-project-id"
state: 1
flytectl update project --file update.yaml --archive
To activate (unarchive), set state: 0 and still pass --archive:
# update.yaml
id: "my-project-id"
state: 0
flytectl update project --file update.yaml --archive
When using a YAML file, the --activate flag is not used. The --archive flag controls whether the state field in the file is applied.
Flags:
FlagDescription
--activateActivate (unarchive) the project
--archiveArchive the project
--nameUpdate the display name
--descriptionUpdate the description
--labelsUpdate labels (key=value)
--filePath to a project YAML definition file
--dryRunPrint the diff without applying changes
--forceSkip the confirmation prompt

update launchplan

Activate or deactivate a versioned launch plan to enable or disable its schedule.
# Activate a launch plan (enables the schedule)
flytectl update launchplan -p flytesnacks -d development \
  core.control_flow.merge_sort.merge_sort \
  --version v1 --activate

# Deactivate a launch plan (disables the schedule)
flytectl update launchplan -p flytesnacks -d development \
  core.control_flow.merge_sort.merge_sort \
  --version v1 --deactivate
Flags:
FlagDescription
--versionVersion of the launch plan to update (required)
--activateActivate the launch plan
--deactivateDeactivate the launch plan
--dryRunPrint the request without executing it
--forceSkip the confirmation prompt
You cannot specify both --activate and --deactivate in the same command.

Matchable attribute updates

Matchable resource attributes allow you to override resource defaults at different scopes. All attribute updates require reading a YAML file via --attrFile.
Use flytectl get <attribute> --attrFile <file> to dump the current configuration before updating it.

update task-resource-attribute

Override default and limit CPU/memory for tasks in a project+domain (or project+domain+workflow).
flytectl update task-resource-attribute --attrFile tra.yaml
tra.yaml (project+domain scope):
domain: development
project: flytesnacks
defaults:
  cpu: "1"
  memory: "150Mi"
limits:
  cpu: "2"
  memory: "450Mi"
tra.yaml (project+domain+workflow scope):
domain: development
project: flytesnacks
workflow: core.control_flow.merge_sort.merge_sort
defaults:
  cpu: "1"
  memory: "150Mi"
limits:
  cpu: "2"
  memory: "450Mi"

update cluster-resource-attribute

Override cluster resource attributes (custom template variables injected into Kubernetes resources).
flytectl update cluster-resource-attribute --attrFile cra.yaml
cra.yaml:
domain: development
project: flytesnacks
attributes:
  foo: "bar"
  buzz: "lightyear"

update execution-cluster-label

Pin executions for a project+domain to a specific cluster.
flytectl update execution-cluster-label --attrFile ecl.yaml
ecl.yaml:
domain: development
project: flytesnacks
value: foo
ecl.yaml (workflow scope):
domain: development
project: flytesnacks
workflow: core.control_flow.merge_sort.merge_sort
value: foo

update execution-queue-attribute

flytectl update execution-queue-attribute --attrFile eqa.yaml

update plugin-override

flytectl update plugin-override --attrFile po.yaml

update workflow-execution-config

flytectl update workflow-execution-config --attrFile wec.yaml
Common attribute file flags:
FlagDescription
--attrFilePath to the attribute YAML file (required)
--dryRunPrint the request without executing it
--forceSkip the confirmation prompt

Build docs developers (and LLMs) love