dynamic networks should fail fast if required properties are not present

[cloudfoundry]

dynamic networks should fail fast if required properties are not present

[ljfranklin]

@robdimsdale yep, looks like it assumes a network named default.

I know we've had passing conversations in the past around BOSH erroring if you give it a property it doesn't know about, e.g. subnets in a dynamic network or typing disk_type instead of persistent_disk_type. Being strict about accepting unknown properties could fix a whole class of UX errors like this one. Not sure if any such validation is planned however.

[johnsonj]

Closing due to age. Please re-open if it's still relevant.

This default behavior is intended, if a default network exists in a GCP project we assign it. I think in practice it's not very useful.

Performing property validation is a long tail/tricky problem. It looks like bosh is moving away from people writing their own manifests so this problem should become less and less of an issue. I'm somewhat in the camp here of: let the IaaS validate it because it ultimately has the final say if it's valid, let the CPI be a thin wrapper.