Adding customizable resources

For background on customizable resources, see How do I configure my Flyte deployment to have specialized behavior per project/domain?. As a quick refresher, custom resources allow you to manage configurations for specific combinations of user projects, domains and workflows that override default values. Examples of such resources include execution clusters, task resource defaults, and more.


Let’s say you want to inject a default priority annotation for your workflows. Perhaps you start off with a model where everything has a default priority but soon you realize it makes sense that workflows in your production domain should take higher priority than those in your development domain.

Now one of your user teams comes to you and wants to ensure that their critical workflows have even higher priority than other production workflows. Here’s how you could go about building a customizable priority designation.

Flyte IDL

You’ll want to introduce a new matchable attribute, including a unique enum value and proto message definition. For example

enum MatchableResource {

message WorkflowPriorityAttribute {
  int priority = 1;

message MatchingAttributes {
  oneof target {
    WorkflowPriorityAttribute WorkflowPriority = 11;

See the changes in this file for an example of what is required.

Flyte admin

Once your idl changes are released, update the logic of flyteadmin to fetch your new matchable priority resource and use it when creating executions or wherever makes sense for your use case.

For example:

resource, err := s.resourceManager.GetResource(ctx, managerInterfaces.ResourceRequest{
    Domain:       domain,
    Project:      project, // optional
    Workflow:     workflow, // optional, must include project when specifying workflow
    LaunchPlan:   launchPlan, // optional, must include project + workflow when specifying launch plan
    ResourceType: admin.MatchableResource_WORKFLOW_PRIORITY,

if err != nil {
    return err

if resource != nil && resource.Attributes != nil && resource.Attributes.GetWorkflowPriority() != nil {
     priorityValue := resource.Attributes.GetWorkflowPriority().GetPriority()
     // do something with the priority here


For convenience, add a flyte-cli wrapper for updating your new attribute. See this PR for the full required set of changes.

That’s it! You now have a new matchable attribute you can configure as the needs of your users evolve.