Delete Quarkus configuration property
org.openrewrite.quarkus.DeleteQuarkusProperty
Delete a property from Quarkus configuration files.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-quarkus
version: 2.4.0
Options
Type | Name | Description | Example |
---|---|---|---|
| propertyKey | The name of the property key whose value is to be deleted. |
|
| oldValue | Optional. Only delete the property value if it matches the configured |
|
| profile | Optional. The profile where the property should be deleted. If not specified, the property will be deleted from all profiles by default. |
|
| deleteFromAllProfiles | Optional. If set to true, the property will be removed from all available profiles. Defaults to |
|
| pathExpressions | Optional. Each value in this list represents a glob expression that is used to match which files will be modified. If this value is not present, this recipe will query the execution context for reasonable defaults. ("/application.yml", "/application.yaml", "/application.properties" and "/META-INF/microprofile-config.properties". |
|
Usage
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.DeleteQuarkusPropertyExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.DeleteQuarkusPropertyExample
has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-quarkus:2.4.0 in your build file:
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform 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.
Contributors
Adriano Machado, Guillaume Smet, Tim te Beek
Last updated