[Request] Read-only Event Templates from mounted volume

[andrewazores]

Describe the feature

Previous versions of Cryostat stored custom event template configuration files directly in the container's filesystem, which would in practice be a mounted volume. The Operator used this fact to provide a feature allowing users to pre-populate the volume with event templates.

Now that custom event templates are stored in S3 object storage it is impractical for the Operator to directly mount the event templates into the storage location. However, the Operator can (and still does) continue to provide a volume mount containing the event template files. Cryostat can either read these files at startup and try to upload them into S3 storage, or it can use them as an additional store location.

Anything other information?

No response

[andrewazores]

Also related, since the "mounted volume" concept is the same, is #330 / #355 . The Operator shares application TLS certificates with Cryostat in the same way, so we must validate that 3.0's implementation still reads from the same location where the Operator mounts them.

[andrewazores]

Looks like the Operator's truststore mounting mechanism still works as expeted.