You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: