[GitHub] [camel-website] orpiske commented on a diff in pull request #913: Camel 3.19 - whats new.

[GitBox <gi...@apache.org>]

orpiske commented on code in PR #913:
URL: https://github.com/apache/camel-website/pull/913#discussion_r990609355


##########
content/blog/2022/10/camel319-whatsnew/index.md:
##########
@@ -0,0 +1,109 @@
+---
+title: "Apache Camel 3.19 What's New"
+date: 2022-10-10
+authors: [davsclaus,gzurowski,essobedo,oscerd]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel 3.19 release.
+---
+
+Apache Camel 3.19 has just been [released](/blog/2022/10/RELEASE-3.19.0/).
+
+This release introduces a set of new features and noticeable improvements that we will cover in this blog post.
+
+## Camel JBang (Camel CLI)
+
+In this release we continue the expansion of Camel CLI.
+
+You can now easily manage local running Camel integrations.
+
+For example to list all running Camel processes:
+
+    camel ps
+    PID   NAME                          READY  STATUS    AGE
+    61818  sample.camel.MyCamelApplica…   1/1   Running  26m38s
+    62506  dude                           1/1   Running   4m34s
+
+To see a bit more information, you can use `camel get`.
+
+Suppose you have two running integrations, then you can manage them, such as stop (with `camel stop <integration-name-or-pid>`),
+or stop/start routes (with respectively `camel cmd stop-route --id=<id-route> <integration-name-or-pid>`/`camel cmd start-route --id=<id-route> <integration-name-or-pid>`) etc:
+
+    camel stop dude
+    Stopping running Camel integration (pid: 62506)
+
+There is a lot more that Camel JBang can do, so make sure to see the [Camel JBang documentation](/manual/camel-jbang.html).
+It is also a good idea to run `camel --help` to list all available commands.
+
+There you can also find information how to get JBang installed, and after that install the Camel app in JBang.
+
+### Camel File
+
+The `camel-file` component has been optimized on the consumer scanning for files,
+to lazy evaluate file size/modification, which often yields better performance,
+as file filtering is usually only based on file names.
+
+### Camel Salesforce
+
+When querying from salesforce, Camel can now sniff the query result and detect the correct DTO class to use
+for deserializing the response, alleviating the need to provide sObjectClass and sObjectName options.
+
+### Rest DSL
+
+It is now possible to inline routes in Rest DSL which means that a Rest service corresponds to 1 route,
+and not 2 as before. This requires to enable `inline-routes=true` in Rest configuration,
+and to link the routes using `direct` endpoints.
+
+### Security
+
+We have upgraded to `TLSv1.3` as default in all components that are using SSL/TLS.
+
+### Load properties from vault/secrets cloud services
+
+In 3.19.0, we introduced the feature of automatically reloading context on Secrets update events on Cloud Services.
+
+We currently support this for AWS Secrets Manager, Google Secret Manager and Azure Key Vault.
+
+The features are using some of the services provided on the cloud
+
+- For AWS, we're leveraging AWS Cloudtrail
+- For GCP, we're leveraging Google Pubsub
+- For Azure Key Vault, we're leveraging Azure Eventgrid and Azure Eventhubs
+
+We provide some [Examples](https://github.com/apache/camel-examples/tree/main/examples/vault) in our camel-examples repository.
+
+**NOTE:**
+The context reloading feature is implemented as general functionality, which means, that its possible
+to use for other use-cases.
+
+### Camel Kafka
+
+We upgraded to Kafka Clients 3.2.x.
+Various other improvements and bug fixes as well, such as better error messages with health checks.
+

Review Comment:
   ### Camel Telegram 
   
   We migrated the external HTTP client used by this component to the HTTP client provided by the JVM. 



-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org