Enhancements: Example Config File, Default Path, and Error Handling Improvements

[maxlambrecht]

This PR add improvements to the java-spiffe-helper:

• Example Config File: Added an example config file for user convenience.
• Default Path for --config Parameter.
• Improved Error Handling: Enhanced error messages and added exception stack trace logging for better error diagnosis.
• Minor refactors and improvements in the code.

[kfox1111]

I can't tell from a quick skim of the patch, where its going to try to read the default config file from in a containerized environment.

Where is it going to look?

[maxlambrecht]

I can't tell from a quick skim of the patch, where its going to try to read the default config file from in a containerized environment.

Where is it going to look?

In a containerized environment, the code will attempt to read the default config file from conf/java-spiffe-helper.conf, and it will look for this file relative to the current working directory.

[kfox1111]

I can't tell from a quick skim of the patch, where its going to try to read the default config file from in a containerized environment.
Where is it going to look?

In a containerized environment, the code will attempt to read the default config file from conf/java-spiffe-helper.conf, and it will look for this file relative to the current working directory.

It would be better I think if the user didn't have to read a Dockerfile to try and find where that is? Defaulting to something more well defined like /etc/java-spiffe-helper.conf would help make it more concrete out of the box?

[maxlambrecht]

I can't tell from a quick skim of the patch, where its going to try to read the default config file from in a containerized environment.
Where is it going to look?

In a containerized environment, the code will attempt to read the default config file from conf/java-spiffe-helper.conf, and it will look for this file relative to the current working directory.

It would be better I think if the user didn't have to read a Dockerfile to try and find where that is? Defaulting to something more well defined like /etc/java-spiffe-helper.conf would help make it more concrete out of the box?

The java-spiffe-helper can be used both in containers and as a standalone JAR. For ease of use, it defaults to the conf/java-spiffe-helper.conf configuration file, as outlined in the README in this PR. This is makes it straightforward to use right away:

> ./gradlew build
> java -jar java-spiffe-helper/build/libs/java-spiffe-helper-0.8.4-osx-aarch_64.jar

[kfox1111]

If you want to do that for non containers, then I think the command suggestion in #187 is still the right thing to do for the containerized side then.

[rturner3]

Can this file have extension .properties rather than .conf? Java properties files typically have the .properties suffix.

[maxlambrecht]

👍