Andrea Cosentino created CAMEL-23583:
----------------------------------------

             Summary: 
camel-google-{functions,secret-manager,vision,text-to-speech,speech-to-text} - 
align Exchange header constant names with Camel naming convention
                 Key: CAMEL-23583
                 URL: https://issues.apache.org/jira/browse/CAMEL-23583
             Project: Camel
          Issue Type: Improvement
          Components: camel-google
            Reporter: Andrea Cosentino
            Assignee: Andrea Cosentino
             Fix For: 4.21.0


Five sibling Google Cloud components expose {{OPERATION}} dispatch headers 
whose values are already in a {{GoogleCloud*}} / {{GoogleSecretManager*}} shape 
but not the {{CamelGoogle*}} prefix that sibling components 
({{camel-google-vertexai}}, {{camel-google-pubsub}}, {{camel-google-bigquery}}) 
already adopt:

* {{camel-google-functions}}: {{OPERATION = "GoogleCloudFunctionsOperation"}}, 
{{ENTRY_POINT = "GoogleCloudFunctionsEntryPoint"}}, {{RUNTIME = 
"GoogleCloudFunctionsRuntime"}}, {{SOURCE_ARCHIVE_URL = 
"GoogleCloudFunctionsSourceArchiveUrl"}}
* {{camel-google-secret-manager}}: {{OPERATION = 
"GoogleSecretManagerOperation"}}
* {{camel-google-vision}}: {{OPERATION = "GoogleCloudVisionOperation"}}
* {{camel-google-text-to-speech}}: {{OPERATION = 
"GoogleCloudTextToSpeechOperation"}}
* {{camel-google-speech-to-text}}: {{OPERATION = 
"GoogleCloudSpeechToTextOperation"}}

Rename string values to {{CamelGoogleCloudFunctions*}} / 
{{CamelGoogleSecretManager*}} / {{CamelGoogleCloudVision*}} / 
{{CamelGoogleCloudTextToSpeech*}} / {{CamelGoogleCloudSpeechToText*}}. Bundle 
as one cross-module PR for family consistency.

h3. Fix shape

Rename the *string value* of each producer-read header constant to 
{{Camel<Component><Name>}}; keep the Java field name unchanged so routes that 
reference the constants symbolically continue to compile and run. Update tests 
that use the literal string values; regenerate component catalog JSON and docs; 
add an upgrade-guide entry in {{camel-4x-upgrade-guide-4_21.adoc}} (and 
matching 4_18 / 4_14 for backports where the component existed in those 
branches).

h3. References

* Tracker: CAMEL-23577
* Precedent (rename pattern): CAMEL-23526 (camel-cxf)
* Alternative pattern (HeaderFilterStrategy approach): CAMEL-23532 
(camel-vertx-websocket / camel-atmosphere-websocket / camel-iggy)




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to