Skip to content

cloud_controller-config.yml.erb assumes the node is also a DEA #6

@andreacampi

Description

@andreacampi

Setting up a CC which is not also a DEA fails when trying to access node[:cloudfoundry_dea][:runtimes].

IMHO it doesn't make much sense to fill in the CC's runtimes attribute based on the runtimes available on a particular DEA.
For instance, say we have 2 DEAs dedicated to Rails and 2 DEAs dedicated to Node.
That's a supported setup in CF, and the CC should be configured to offer both.

Setting the attribute explicitly on the CC works, naturally.
Ideally, we should find DEAs with a search and configure the CF with the union of all available runtimes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions