Skip to content

Implement dynamic resources support #2450

@kevinchalet

Description

@kevinchalet

Confirm you've already contributed to this project or that you sponsor it

  • I confirm I'm a sponsor or a contributor

Describe the solution you'd like

Currently, resources must be statically registered (by calling options.RegisterResources(...)), which is fine for simple setups but not ideal for larger deployments. To address that, we'll need to introduce a new Resource entity/manager/store, very similar to what currently exists for the Scope entity/manager/store.

(since it requires a schema change, it will have to wait until 8.0)

Additional context

No response

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions