Switch docs and samples to use CORS and JSON enabled properties

[wjglerum]

Recently quarkus.http.cors=true was updated to quarkus.http.cors.enabled=true.

This PR also reflects that in the docs, tests and samples. We should probably do the same for the log properties quarkus.log.*.json

https://quarkus.io/blog/quarkus-3-19-1-released/#migration-to-configmapping
https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19#other-changes-gear-white_check_mark

Not sure what to do with the SmallRyeOpenApiProcessor as it does not check for the new property (yet), should we for compatibility check both?

[sberyozkin]

Thanks @wjglerum, IMHO at least one CORS test should continue testing the old property, which is still likely to be used a lot, even though it is deprecated

[wjglerum]

Thanks @wjglerum, IMHO at least one CORS test should continue testing the old property, which is still likely to be used a lot, even though it is deprecated

Good point, will add a basic one 👍

[gsmet]

We should probably do the same for the log properties quarkus.log.*.json

Yes, if you have the time, please do!

[wjglerum]

We should probably do the same for the log properties quarkus.log.*.json

Yes, if you have the time, please do!

Will do that too then, would you prefer a separate PR or shall I combine it with this one?

[gsmet]

Looks good to me.

I agree with Sergey that it would be nice to have a small test (one is enough!) for the deprecated config. I would just copy an existing one and be done with it.

[github-actions]

🙈 The PR is closed and the preview is expired.

[wjglerum]

I agree with Sergey that it would be nice to have a small test (one is enough!) for the deprecated config. I would just copy an existing one and be done with it.

Just added that 👍

[wjglerum]

@gsmet this should be ready now

[gsmet]

Thanks!

[gsmet]

I rebased to squash the fix commit to sort the imports. Will merge tomorrow.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit f8c608c.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f8c608c.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[gsmet]

Thanks a lot!