After upgrading from v0.9.5 to v0.9.6 existing secrets cannot be decrypted anymore using UI ingestion:

"Failed to resolve secret with name {match}. Aborting recipe execution."

After recreating those secrets it works again.

Following up on a possible scenario where the default secret is being set to an empty string rather than the traditional default value. Specifically this setting was recently updated to ensure proper escaping of the secret value in the case of some special characters used in Spring’s SPEL parsing.

I am running into the same issue. I guess the workaround is recreating secrets but perhaps there's a better solution?

Working on a release, the fix is ultimately committed here. That built an image from master with tag

e23eb71

, however working to create a release with that fix cherry-picked