Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task] Development and CI runs should use h2:file mode by default #1094

Closed
andrewazores opened this issue Oct 5, 2022 · 0 comments · Fixed by #1096
Closed

[Task] Development and CI runs should use h2:file mode by default #1094

andrewazores opened this issue Oct 5, 2022 · 0 comments · Fixed by #1096
Assignees
Labels
chore Refactor, rename, cleanup, etc.

Comments

@andrewazores
Copy link
Member

h2:file is more representative of a real Cryostat deployment than h2:mem is, since persistence would generally be wanted for the JMX credentials keyring at least and also for the discovery database (especially custom targets). The Operator will deploy in h2:file mode when there is an associated PVC and storage space to put the file on:

cryostatio/cryostat-operator#451

h2:mem should remain a configurable option and should also be easily selectable for development since it may also have its own uses for "ephemeral" Cryostat instances.

@andrewazores andrewazores added the chore Refactor, rename, cleanup, etc. label Oct 5, 2022
@andrewazores andrewazores self-assigned this Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Refactor, rename, cleanup, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant