Delete property
org.openrewrite.yaml.DeleteProperty Delete a YAML property. Nested YAML mappings are interpreted as dot separated property names, i.e. as Spring Boot interprets application.yml files like
a.b.c.d
or a.b.c:d
.- groupId: org.openrewrite
- artifactId: rewrite-yaml
- version: 7.38.0
Type | Name | Description |
---|---|---|
String | propertyKey | The key to be deleted. |
Boolean | coalesce | Optional. (Deprecated: in a future version, this recipe will always use the false behavior) Simplify nested map hierarchies into their simplest dot separated property form. |
Boolean | relaxedBinding | Optional. Whether to match the propertyKey using relaxed binding rules. Default is true . Set to false to use exact matching. |
String | fileMatcher | Optional. Matching files will be modified. This is a glob expression. |
This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your
rewrite.yml
create a new recipe with a unique name. For example: com.yourorg.DeletePropertyExample
. Here's how you can define and customize such a recipe within your rewrite.yml:rewrite.yml
---
type: specs.openrewrite.org/v1beta/recipe
name: com.yourorg.DeletePropertyExample
displayName: Delete property example
recipeList:
- org.openrewrite.yaml.DeleteProperty:
propertyKey: management.metrics.binders.files.enabled
coalesce: null
relaxedBinding: null
fileMatcher: '**/application-*.yml'
Now that
com.yourorg.DeletePropertyExample
has been defined activate it in your build file:Gradle
Maven
build.gradle
plugins {
id("org.openrewrite.rewrite") version("5.38.0")
}
rewrite {
activeRecipe("com.yourorg.DeletePropertyExample")
}
repositories {
mavenCentral()
}
pom.xml
<project>
<build>
<plugins>
<plugin>
<groupId>org.openrewrite.maven</groupId>
<artifactId>rewrite-maven-plugin</artifactId>
<version>4.42.0</version>
<configuration>
<activeRecipes>
<recipe>com.yourorg.DeletePropertyExample</recipe>
</activeRecipes>
</configuration>
</plugin>
</plugins>
</build>
</project>
The Moderne public SaaS instance enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Last modified 5d ago