Skip to main content

Use TLS for AMQP connection strings

org.openrewrite.java.spring.amqp.UseTlsAmqpConnectionString

Use TLS for AMQP connection strings.

Recipe source​

GitHub, Issue Tracker, Maven Central

This recipe is available under the Moderne Source Available License.

Options​

TypeNameDescriptionExample
StringpropertyKeyOptional. The Spring property key to perform updates against. If this value is specified, the specified property will be used for searching, otherwise a default of spring.rabbitmq.addresses will be used instead.spring.rabbitmq.addresses
IntegeroldPortThe non-TLS enabled port number to replace with the TLS-enabled port. If this value is specified, no changes will be made to amqp connection strings which do not contain this port number.1234
IntegerportThe TLS-enabled port to use.1234
StringtlsPropertyKeyOptional. The Spring property key to enable default TLS mode against. If this value is specified, the specified property will be used when updating the default TLS mode, otherwise a default of spring.rabbitmq.ssl.enabled will be used instead.spring.rabbitmq.ssl.enabled
ListpathExpressionsOptional. 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", and "**/application.properties".**/application.yml

Example​

Parameters​
ParameterValue
propertyKeynull
oldPort5672
port5671
tlsPropertyKeynull
pathExpressionsnull
Before​
spring:
  rabbitmq:
    addresses: host1:5672
After​
spring:
  rabbitmq:
    addresses: host1:5671
    ssl:
      enabled: true
Before​
spring.rabbitmq.addresses=host1:5672
After​
spring.rabbitmq.addresses=host1:5671
spring.rabbitmq.ssl.enabled=true

Usage​

This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly (unless you are running them via the Moderne CLI). 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.UseTlsAmqpConnectionStringExample. 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.UseTlsAmqpConnectionStringExample
displayName: Use TLS for AMQP connection strings example
recipeList:
  - org.openrewrite.java.spring.amqp.UseTlsAmqpConnectionString:
      propertyKey: spring.rabbitmq.addresses
      oldPort: 1234
      port: 1234
      tlsPropertyKey: spring.rabbitmq.ssl.enabled
      pathExpressions: **/application.yml

Now that com.yourorg.UseTlsAmqpConnectionStringExample has been defined, activate it and take a dependency on org.openrewrite.recipe:rewrite-spring:6.7.0 in your build file:

  1. Add the following to your build.gradle file:
build.gradle
plugins {
    id("org.openrewrite.rewrite") version("7.6.2")
}

rewrite {
    activeRecipe("com.yourorg.UseTlsAmqpConnectionStringExample")
    setExportDatatables(true)
}

repositories {
    mavenCentral()
}

dependencies {
    rewrite("org.openrewrite.recipe:rewrite-spring:6.7.0")
}
  1. Run gradle rewriteRun to run the recipe.

See how this recipe works across multiple open-source repositories​

Run this recipe on OSS repos at scale with the Moderne SaaS.

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.

Data Tables​

Source files that had results​

org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

Column NameDescription
Source path before the runThe source path of the file before the run. null when a source file was created during the run.
Source path after the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changesIn a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changesThe specific recipe that made a change.
Estimated time savingAn estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
CycleThe recipe cycle in which the change was made.

Contributors​

Shannon Pamperl, Knut Wannheden, Kun Li, Jonathan Schnéider, Nate Danner