Find what blocks a Das Schiff BGPPeering from moving to the Sylva network connector API
Recipe ID
io.moderne.kubernetes.sylva.migrate.dasschiff.FindBgpPeeringMigrationBlockersArtifactorg.openrewrite.recipe:rewrite-kubernetesReport what a human has to decide before a Das Schiff BGPPeering can move to the network-connector.sylvaproject.org group. Nothing is rewritten: the legacy spec.export is a reject-by-default prefix filter and the intent one is accept-by-default BGP communities, so a peering moved as it stands would advertise the whole VRF table.
Single recipeProprietary
Usage
This recipe has no required configuration options. You’ll need the Moderne CLI configured before running the command below.
mod run . --recipe io.moderne.kubernetes.sylva.migrate.dasschiff.FindBgpPeeringMigrationBlockersIf the recipe isn’t available locally, install it with:
mod config recipes jar install org.openrewrite.recipe:rewrite-kubernetes:RELEASEOptions
| Name | Type | Description |
|---|---|---|
fileMatcher | String | Matching files will be searched. This is a glob expression. e.g. **/bgp-*.yml |
Data tables
Structured output this recipe can produce.
- BGP peeringsDeutsche Telekom `network.t-caas.telekom.com` `BGPPeering` resources, and what each one needs decided before it can be written against the `network-connector.sylvaproject.org` `BGPPeering` that shares its name.
io.moderne.kubernetes.sylva.migrate.dasschiff.table.BgpPeerings - Source files that had resultsSource files that were modified by the recipe run.
org.openrewrite.table.SourcesFileResults - Source files that had search resultsSearch results that were found during the recipe run.
org.openrewrite.table.SearchResults - Source files that errored on a recipeThe details of all errors produced by a recipe run.
org.openrewrite.table.SourcesFileErrors - Recipe performanceStatistics used in analyzing the performance of recipes.
org.openrewrite.table.RecipeRunStats