You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User can't know what function that setting provides.
Flyte documents don't have an introduction or quickstart that setting of org, domain and project includes resources, service accounts , apps and etc...
What to do ?
The priority of hierarchy determines the setting results
What fields we have
UNSET indicates the ~unset
how to use flyte cli to view, edit the settings.
edit setting from file
Note
The implementation for supporting setting is ongoing, so fields of the setting are not all applied.
If there are new progress of the implementation to apply the new fields, welcome to add PR reference or comment here.
Suggested documentation should explain that settings are defaults inherited from org → domain → project; narrower scopes can override broader ones. Task/workflow configuration takes precedence, except task_resource.max.*, which are enforced limits. The documented fields include queues, concurrency, service accounts, storage paths, resource minimums/maximums, accelerators, labels, annotations, and environment variables. Apps are not explicitly listed as a settings field in the available sources. See Settings.
Add a CLI quickstart covering viewing, interactive editing, and file-based editing. Omitting a key inherits its parent value; ~unset explicitly clears it and blocks inheritance. CLI settings reference documents flyte get settings and flyte edit settings --from-file.
flyte get settings --domain production
flyte edit settings --domain production
flyte edit settings --domain production --from-file settings.yaml
Activity
runllm commentedon Nov 18, 2026
Suggested documentation should explain that settings are defaults inherited from org → domain → project; narrower scopes can override broader ones. Task/workflow configuration takes precedence, except
task_resource.max.*, which are enforced limits. The documented fields include queues, concurrency, service accounts, storage paths, resource minimums/maximums, accelerators, labels, annotations, and environment variables. Apps are not explicitly listed as a settings field in the available sources. See Settings.Add a CLI quickstart covering viewing, interactive editing, and file-based editing. Omitting a key inherits its parent value;
~unsetexplicitly clears it and blocks inheritance. CLI settings reference documentsflyte get settingsandflyte edit settings --from-file.Sources:
This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.
Mention @Herald to ask follow-up questions. See runllm.com for more!
[-][Document] User guide of Flyte Setting[/-][+][Document] User guide of Flyte Settings[/+]0yukali0 commentedon Nov 18, 2026
#take