Skip to content

Container specific configuration #4

Open
@Legion2

Description

@Legion2

Why is the generic "resources" namespace used for (docker) container specific configurations? resources.volume, resources.image

I think we should also go through all configuration names, currently they are all namespaced with the old phases names from viplab 2. I created the namespaces because I needed a mapping from the old config to the new configuration options in the websocket-api. But now as we completely dropped the support for the old format, we don't need the namespaces in this form, we can look for better names for the configuration options.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions