Skip to content

feature: defaultAPIBindings are only created as initialization #3248

Open
@blut

Description

@blut

Feature Description

I'd like the workspace type as a template for different consumers creating a default binding configuration that is kept up to date with the bindings defined in the workspace type.

Proposed Solution

Ideally, newly added defaultAPIBindings should be propagated to any existing workspace of the type (and extensions?)

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    Status

    New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions