davsclaus opened a new pull request, #30364: URL: https://github.com/apache/camel/pull/30364
[CAMEL-27220](https://issues.apache.org/jira/browse/CAMEL-27220) ## What changed - **`google-sheets:application-x-struct`:** a `spreadsheetId` field in a JSON row no longer chooses the spreadsheet. - The spreadsheet comes from the `CamelGoogleSheets.spreadsheetId` header, or else from the endpoint's `spreadsheetId` option. - The field is still left out of the row values. - Without the header, the transformer no longer sets the spreadsheet id headers to an empty value. - **Producer and consumer:** the credential options are no longer set on the API request: `clientId`, `clientSecret`, `accessToken`, `refreshToken`, `serviceAccountKey` and `delegate`. - So the access token is no longer the `access_token` query parameter. - The OAuth credential of the client sends it in the `Authorization` header, as before. - The shared loop is now `GoogleSheetsEndpoint.configureRequest(...)`. ## Upgrade note Two entries in the 4.24 upgrade guide: - Routes that took the spreadsheet from the body must set `CamelGoogleSheets.spreadsheetId` before the transformer. - A `CamelGoogleSheets.accessToken` header is no longer put on the request. ## Tests - New `GoogleSheetsRequestCredentialTest` uses the real client factory on a recording `MockHttpTransport`. For the producer and the consumer, it checks that the request URL has no `access_token` and that the `Authorization` header is `Bearer <token>`. - `GoogleSheetsJsonStructDataTypeTransformerTest` gets new tests: the header against a row field (the header wins), and no header (no spreadsheet headers set). The existing tests are updated. - Without the change: - the producer test and five transformer tests fail; - the consumer test still passes, because it covers the same code path as the producer. - The module's 54 unit tests and 9 ITs pass. _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
