Skip to content

Ability to constrain selectable blueprints based on requirements #465

@agdimech

Description

@agdimech

Describe your feature request

I have a Blueprint annotated with the @requires jsdoc. It would be amazing to generate a DAG based on these and only render selectable blueprints in the UI.

Describe the solution you'd like

  • A user annotates their blueprint with @requires and specifies 'my-blueprint' as the value.
  • In the UI, if a user is creating a new project - all @requires blueprints should not be selectable as they require a blueprint to already be deployed.
  • in the UI, if a user is adding a blueprint to an existing project, only blueprints which satisfy the @requires should be selectable.

Describe alternatives you've considered

  • Throw an error at synth time (this is not a great UX).

Additional context

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions