How do I create a workflow_execution_config for my project?

flytectl get workflow_execution_config -p project -d domain

fails with

attribute not found

To create a

workflow_execution_config

for your project, first generate a sample config file using

flytectl get workflow-execution-config -p <project> -d <domain> --attrFile wec.yaml --gen

. Then, edit

wec.yaml

as needed (e.g., set

max_parallelism

,

security_context

, etc.). Finally, apply it with

flytectl update workflow-execution-config --attrFile wec.yaml

. The "attribute not found" error simply means no config exists yet, so you need to create and apply one as described above. See example YAML and commands in the linked source. Would you like a step-by-step breakdown or example YAML? Sources: - flytectl/cmd/get/matchable_workflow_execution_config.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 When I run

flytectl get workflow-execution-config -p <project> -d <domain> --attrFile wec.yaml --gen

I get the

attribute not found

error, thus I can't generate the sample config

The

attribute not found

error is expected if no

workflow_execution_config

exists yet for your project/domain. However, when you add the

--gen

flag,

flytectl

should still generate a sample config file (

wec.yaml

) for you, even if the attribute is missing. If the file is not being generated, this may indicate a bug or an issue with your

flytectl

version or usage. The intended behavior is: if the attribute is not found and

--gen

is provided, a sample config should be created. Please check if

wec.yaml

is present after running the command, even if the error appears. If not, consider updating

flytectl

or check for known issues in the repository. See the command logic in the source for details. Would you like a step-by-step troubleshooting guide? Sources: - flytectl/cmd/get/matchable_workflow_execution_config.go 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 give me a step by step troubleshooting guide

It seems likely that the

--gen

flag should generate a sample config file even if the attribute is not found. Here’s a step-by-step troubleshooting guide based on the command logic: 1. Check flytectl Version: Make sure you are using a recent version of

flytectl

, as older versions may not support the

--gen

flag correctly. Update if necessary. 2. Run the Command: Execute

flytectl get workflow-execution-config -p <project> -d <domain> --attrFile wec.yaml --gen

. 3. Check for wec.yaml: Even if you see the

attribute not found

error, look for the

wec.yaml

file in your current directory. The tool should generate this file as a sample config. 4. Inspect wec.yaml: If the file exists, open it and edit the fields as needed (e.g.,

max_parallelism

,

security_context

). 5. Apply the Config: Use

flytectl update workflow-execution-config --attrFile wec.yaml

to create the config in Flyte. 6. If File Not Generated: If

wec.yaml

is not created, try running the command with increased verbosity or check for permission issues in your directory. 7. Check for Known Issues: Review the flytectl source code and issues for any related bugs. 8. Alternative Generation: As a workaround, manually create a sample

wec.yaml

using the example from the source, then apply it with the update command. Example sample config (from the source):

annotations:
  values:
    cliAnnotationKey: cliAnnotationValue
domain: <domain>
labels:
  values:
    cliLabelKey: cliLabelValue
max_parallelism: 10
project: <project>
raw_output_data_config:
  output_location_prefix: cliOutputLocationPrefix
security_context:
  run_as:
    k8s_service_account: default

Sources: - flytectl source code 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.