squakez commented on code in PR #1264:
URL: https://github.com/apache/camel-website/pull/1264#discussion_r1867616295
##########
content/blog/2024/12/camel49-whatsnew/index.md:
##########
@@ -0,0 +1,155 @@
+---
+title: "Apache Camel 4.9 What's New"
+date: 2024-12-06
+authors: [davsclaus,squakez]
+categories: ["Releases"]
+preview: Details of what we have done in the Camel 4.9 release.
+---
+
+Apache Camel 4.9 has just been [released](/blog/2024/12/RELEASE-4.9.0/).
+
+This release introduces a set of new features and noticeable improvements that
we will cover in this blog post.
+
+## Camel Core
+
+Added _startup condition_ feature to let Camel perform some checks on startup,
+before continuing. For example to check if a specific ENV exists, or wait
+for a specific file to be created etc.
+
+The supervised route controller now emits `RouteRestartingEvent` when routes
are attempted to be
+started again after a previous failure. This allows to have _fined grained_
events for what happens.
+
+Added a _trust all certificate_ option for Camel SSL. To make it quick
+to use HTTPS but without having a valid certificate. Only use this for
development purposes.
+
+The route dumper to XML and YAML no longer includes nodes with default values
in the output.
+
+## DSL
+
+You can now globally configure data formats in XML and YAML DSL also, which
makes it easier to
+set up your data formats once, and reuse these within all your routes by
referring to their ids.
+
+## Camel Test
+
+We have made it easier to use fluent builders with mock endpoints to set
expectations using Camel languages such as
+JSonPath, JQ, XPath, Simple, etc. See `camel-mock` documentation for more
details.
+
+## Camel JBang
+
+When showing _help_ (such as `camel get route --help`) then all the default
values is now shown in the help text.
+
+The `camel get properties` can now show property placeholder values with
default vs actual value, such
+as when values are applied from ENV variables. This makes it possible to
better track how a value was configured.
+
+TODO: repl command
+TODO: receive command
+
+### Camel JBang Kubernetes
+
+TODO:
+
+## Camel Observability Services
+
+One of the main challenges of running a Microservices Oriented Architecture on
cloud is to monitor how the different services deployed are interacting
together. During the last years we have worked to introduce several components
that cover the **Observability** stack. However all the different components
contributing to the observability services had to be configured each of them
separately. Even worse, each of the different runtimes we support in Camel
(Main, Quarkus, Spring Boot) had its own configuration and its own endpoints.
+
+The new component we're introducing in this release,
`camel-observability-services` has the goal to uniform and harmonize the
configuration and to provide a set of default configuration that are the same
regardless the runtime of choice. This is going to be particularly handy when
you need to manage Camel on the cloud, providing a set of opinionated tools
with default settings. So far, when you are using this component, you're going
to use these components out of the box:
+
+* `camel-health`
+* `camel-management`
+* `camel-micrometer-prometheus`
+* `camel-opentelemetry`
+
+Read the manual to get more information about [how to do observability with
Camel](xref:components::observability-services.adoc).
+
+NOTE: the component will require an extension and will be available on Quarkus
runtime with the first release of Camel Quarkus supporting 4.9.0 which should
be done some week after this core release.
+
+## ????
+
+TODO: stuff here
+
+## Camel Groovy
+
+We have aligned the syntax to use same naming pattern as the simple language,
which makes it easier
+to use both languages with Camel. This means you can refer to exchange,
headers, variables in the same way.
+
+Added `log` function to make it easy to write to log from within a groovy
script.
+
+For low-code users that favour using Groovy then we made it possible to use
the Log EIP with groovy instead of simple.
+You can configure this with `camel.main.logLanguage = groovy`.
+
+The Log EIP now formats the `${exchange}` output using the standard exchange
formatter, which makes
+it easier to see the content of the current `Exchange`.
+
+## Camel JMS
+
+The JMS component will now default filter out `CamelXXX` headers as done by
other Camel components.
+
+## Camel HTTP
+
+The `camel-http` component now supports caching and refreshing OAuth2 tokens.
+
+## Security Vaults
+
+In the `camel-kubernetes` you can now let Camel be auto-reloaded on configmap
updates, just as it was possible with secret updates.
+
+In Camel Spring Boot you can use security vaults to store configuration
values, which now can also be used in Spring configurations
+such as `spring.datasource.password = {{aws:myDatabasePassword}}`
+
+## Camel Kamelets
+
+We have moved `kamelets-utils` from Camel Kamelets to Camel Core project
(inside `camel-kamelets`) to make it easier to maintain,
+and also because Kamelets are first-class everywhere with Camel.
+
+You can now configure kamelets with ENV variables using a more human ready for
lang parameters.
+
+The option `bucketNameOrArn` can now be configured using both of the following
styles:
+
+```properties
+CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN = myBucket
+CAMEL_KAMELET_AWS_S3_SOURCE_BUCKET_NAME_OR_ARN = myBucket
+```
+
+This actually applies to all the Camel configuration you can (not only for
kamelets).
Review Comment:
```suggestion
This actually applies to all the Camel configuration you can (not only for
Kamelets).
```
--
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]
