You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There are many parameters that one might want to tweak on the Galaxy custom resource when restoring from a backup.
Currently the only way to achieve this would be to run a pod, mount the backup, edit the backup files directly, then terminate that pod and run a restore. This is cumbersome.
Describe the solution you'd like
We should make it possible to override galaxy.spec parameters on the new custom resource created during the restore role.
Additional context
cc @kurokobo This may be useful for the awx-on-k3s roles if you ever want to restore with a deployment_name different from the original deployment, because with pre-created hostMount volumes I think you need to change the *_storage_class params to use the new pvc.
file_storage_storage_class
postgres_storage_class
redis_storage_class
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There are many parameters that one might want to tweak on the Galaxy custom resource when restoring from a backup.
Currently the only way to achieve this would be to run a pod, mount the backup, edit the backup files directly, then terminate that pod and run a restore. This is cumbersome.
Describe the solution you'd like
We should make it possible to override galaxy.spec parameters on the new custom resource created during the restore role.
Additional context
cc @kurokobo This may be useful for the awx-on-k3s roles if you ever want to restore with a deployment_name different from the original deployment, because with pre-created hostMount volumes I think you need to change the
*_storage_class
params to use the new pvc.The text was updated successfully, but these errors were encountered: