Quarkus Gradle Plugin: tests with encrypted configuration

[snazy]

As decribed in #33135, using encrypted configuration values did not work with the Gradle plugin since Quarkus 3.0.0, prior to SmallRye Config 3.3.0 (#33079).

This change just adds tests to validate the behavior.

[snazy]

Setting this to draft, because I want to add a test that has a "real" encrypted value and validate it.

[radcortez]

I probably need to add a way to completely disable secret handler expressions at the builder level, because this will happen with other handler names found in the configuration, so setting a fake for aes-gcm-nopadding is not going to be enough.

[snazy]

setting a fake for aes-gcm-nopadding is not going to be enough.

I suspected that this will be the case.

completely disable secret handler expressions at the builder level,

Hm - yea - that deserves a change in SmallRyeConfigBuilder.

[radcortez]

smallrye/smallrye-config#937

[snazy]

Updated the PR to only add tests verifying the behavior.

[gsmet]

Let's rebase and get another CI run.

[gsmet]

We can get this in provided CI is happy about it.

[gastaldi]

@snazy can you rebase with the latest main before we merge this?

[snazy]

@snazy can you rebase with the latest main before we merge this?

@gastaldi done

[gastaldi]

Looks like CI doesn't like it, can you verify @snazy ?

[snazy]

Oh yea - the crypto-tests now fail with Caused by: java.util.NoSuchElementException: SRCFG00046: Could not find a secret key handler for aes-gcm-nopadding - seems that #38007 is actually a regression, based on the original commit message for this PR :(

[quarkus-bot]

Status for workflow Quarkus CI

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

✅ 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.

[gastaldi]

Thanks!