Composes a VPC, three subnets, and a security group, where the subnets and security group depend on the VPC's ID. See the Basic Example in the top-level README for the full walkthrough on a live cluster.
Start function-kro from the repository root:
go run . --insecure --debugRender the example:
cd example/basic
crossplane render -r -x xr.yaml composition.yaml functions.yaml --required-schemas=schemas/This renders the composite and the VPC. The subnets and security group read
${vpc.status.atProvider.id}, which is empty until a provider creates the VPC,
so render defers them.
Add --observed-resources=observed.yaml to supply provider-assigned IDs, as a
cluster would:
crossplane render -r -x xr.yaml composition.yaml functions.yaml --required-schemas=schemas/ --observed-resources=observed.yamlNow the whole graph renders and status.networkingInfo fills in with the VPC,
subnet, and security group IDs.