oscerd opened a new pull request, #23467:
URL: https://github.com/apache/camel/pull/23467

   ## Summary
   
   Renames the Exchange header string values in the five Google Cloud component
   constant classes from their `GoogleCloud<Service>` / `GoogleSecretManager`
   prefixes — which sit **outside** the `Camel` namespace and are therefore not
   filtered by the default `HeaderFilterStrategy` at transport boundaries — to
   `CamelGoogle<Service><Name>`. This follows the convention used across the 
rest
   of the Camel component catalog and matches the pattern established in
   CAMEL-23526 (`camel-cxf`), CAMEL-23522 (`camel-mail`), CAMEL-23461
   (`camel-aws-bedrock`), CAMEL-23532 (`camel-vertx-websocket` /
   `camel-atmosphere-websocket` / `camel-iggy`), and CAMEL-23576 (`camel-jira`).
   
   | Constant | Previous value | New value |
   |----------|----------------|-----------|
   | `GoogleCloudFunctionsConstants.OPERATION` | 
`GoogleCloudFunctionsOperation` | `CamelGoogleCloudFunctionsOperation` |
   | `GoogleCloudFunctionsConstants.ENTRY_POINT` | 
`GoogleCloudFunctionsEntryPoint` | `CamelGoogleCloudFunctionsEntryPoint` |
   | `GoogleCloudFunctionsConstants.RUNTIME` | `GoogleCloudFunctionsRuntime` | 
`CamelGoogleCloudFunctionsRuntime` |
   | `GoogleCloudFunctionsConstants.SOURCE_ARCHIVE_URL` | 
`GoogleCloudFunctionsSourceArchiveUrl` | 
`CamelGoogleCloudFunctionsSourceArchiveUrl` |
   | `GoogleCloudFunctionsConstants.RESPONSE_OBJECT` | 
`GoogleCloudFunctionsResponseObject` | 
`CamelGoogleCloudFunctionsResponseObject` |
   | `GoogleSecretManagerConstants.OPERATION` | `GoogleSecretManagerOperation` 
| `CamelGoogleSecretManagerOperation` |
   | `GoogleCloudVisionConstants.OPERATION` | `GoogleCloudVisionOperation` | 
`CamelGoogleCloudVisionOperation` |
   | `GoogleCloudVisionConstants.RESPONSE_OBJECT` | 
`GoogleCloudVisionResponseObject` | `CamelGoogleCloudVisionResponseObject` |
   | `GoogleCloudTextToSpeechConstants.OPERATION` | 
`GoogleCloudTextToSpeechOperation` | `CamelGoogleCloudTextToSpeechOperation` |
   | `GoogleCloudTextToSpeechConstants.RESPONSE_OBJECT` | 
`GoogleCloudTextToSpeechResponseObject` | 
`CamelGoogleCloudTextToSpeechResponseObject` |
   | `GoogleCloudSpeechToTextConstants.OPERATION` | 
`GoogleCloudSpeechToTextOperation` | `CamelGoogleCloudSpeechToTextOperation` |
   | `GoogleCloudSpeechToTextConstants.RESPONSE_OBJECT` | 
`GoogleCloudSpeechToTextResponseObject` | 
`CamelGoogleCloudSpeechToTextResponseObject` |
   
   The Java field names are unchanged, so routes referencing the constants
   symbolically continue to work; routes using the literal string values must be
   updated (documented in the 4.21 upgrade guide).
   
   ## Already-compliant constants left unchanged
   
   `GoogleSecretManagerConstants.SECRET_ID`, `VERSION_ID` and `REPLICATION` were
   already `Camel`-prefixed (`CamelGoogleSecretManagerSecretId`, etc.).
   
   ## DSL accessors
   
   The generated Endpoint DSL header accessor **names are unchanged** (e.g.
   `googleCloudFunctionsOperation()`), because the `Camel` prefix is stripped
   when deriving the accessor name; the accessors now return the new
   `Camel`-prefixed values.
   
   ## Backports
   
   - `camel-google-functions` and `camel-google-secret-manager` exist on
     `camel-4.18.x` and `camel-4.14.x` with the same legacy values — backport
     applies and will be filed as follow-up PRs.
   - `camel-google-vision`, `camel-google-text-to-speech` and
     `camel-google-speech-to-text` were added after the 4.18.x / 4.14.x branch
     points and **do not exist** on those branches — no backport for them.
   
   ## Test plan
   
   - [x] `mvn test` in each of the 5 modules — all pass
   - [x] Module + catalog + endpointdsl built cleanly; only the 5 Google
         components' regen artifacts included
   - [x] Tests use symbolic constant references, so no test changes needed
   - [x] Upgrade guide entry added documenting all 12 value changes
   
   Tracker: CAMEL-23577
   
   _Reported by Claude Code on behalf of Andrea Cosentino_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to