Skip to content

Orchestrator version should be based on Metadata #320

@marvinkruse

Description

@marvinkruse

Like in a module, we should probably use the Metadata functionality for the Orchestrator as well, since currently, it's just a hardcoded number that represents its version.

Metadata

Metadata

Assignees

Labels

changesUpdates to a feature or mechanismlow prio

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions