Posting in containers but if dev is more appropriate, please feel free to move this.
Dear all, I’ve been working on the Dataverse Action and have improved its structure and functionality. Previously, it wasn’t possible to gather logs because the action was composite-based and couldn’t run post actions. This implementation migrates to a Node-based backend, which allows post actions and, in my opinion, offers a more flexible solution.
Another addition is the ability to enable S3 storage, currently limited to LocalStack. This feature provides two options:
localstack.The implementation of this feature has been quite challenging. The MicroProfile directory-based approach previously implemented didn’t work unfortunately. @Oliver Bertuch I’m not an expert in Payara, but it seems that the Dataverse instance doesn’t recognize the secrets. Currently, I simply manipulate the compose YAML at runtime, which may not be the most elegant solution, but it works.
I’ve added tests to verify the addition of JVM arguments and a small Python test suite to ensure that functionalities like S3 storage are functioning correctly.
It would be great if someone could review this, as I’d like to update the action for use in my other libraries, which partially depend on S3 uploads. Leaving it untested in the CI doesn’t feel right.
Here’s the pull request:
https://github.com/gdcc/dataverse-action/pull/18
@Philip Durbin 🚀 - @Jan Range and I want to chat about this in ~20-30 minutes. Do you want in?
Sure! Is it too late?
https://fz-juelich-de.zoom-x.de/j/61896738935?pwd=gwP8O5bc4z6ZgOgb7Db57QAFEx0YxT.1
Last updated: Oct 30 2025 at 05:14 UTC