Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Network for Route cannot be selected via networkSelector #77

Open
wolfmayr opened this issue Sep 26, 2022 · 0 comments
Open

Network for Route cannot be selected via networkSelector #77

wolfmayr opened this issue Sep 26, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@wolfmayr
Copy link

What problem are you facing?

I am trying to create a composition with a Network and a Route resource. In the Route resource, I would like to select the network which is created in the same composition via a networkSelector. Similarly to the way it is possible for a Subnetwork resource for example. At the moment this is not possible - instead I have to specify the exact name of the network in the network field of the route. However, I do not know the network name at the time of configuring the route, since the network name is auto-generated and can't be specified when configuring the network resource.

How could GCP Provider help solve your problem?

This problem could be solved by adding a networkSelector to the Route resource, similar to how it is implemented for a Subnetwork or a Firewall resource.

Additionally, the network field would have to be changed from a required to an optional field.

Resources:

Subnetwork, where the networkSelector is available under forProvider: https://doc.crds.dev/github.com/crossplane-contrib/provider-jet-gcp/compute.gcp.jet.crossplane.io/Subnetwork/[email protected]

Route, where the networkSelector is missing: https://doc.crds.dev/github.com/crossplane-contrib/provider-jet-gcp/compute.gcp.jet.crossplane.io/Route/[email protected]

@wolfmayr wolfmayr added the enhancement New feature or request label Sep 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant