lburgazzoli commented on issue #3981: URL: https://github.com/apache/camel-k/issues/3981#issuecomment-1456080425
> am I understanding correctly base64 is basically to circumvent the `.properties` limitation on newlines/whitespace/indentation, and basically guarantee the JSON representation (string) can be placed on 1-single line (for the .properties)? > > If that understanding is correct, is fine with me with base64 or other encoding, and granted, is up to the consumer of that configuration item to be aware it's a JSON representation which need decoding in some way (which is typically the case, as a developer accessing a configuration parameter). At that point the developer could decode using Jackson by providing a marshalling class when known, or decode using Jackson by unmarshalling to generic JSONNode or Map. No, camel-k should do the necessary configuration magic to ensure the user does not need to worry about base64 encoding. What the user's bean would receive is either a plain string/bytes or a decoded object if a related type converter is provided. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
