-
Notifications
You must be signed in to change notification settings - Fork 39
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
Update dependency charts; save outputs to working dir #501
base: master
Are you sure you want to change the base?
Conversation
I don't understand what's going on with the tests so I hope it is transient. What worked a few hours ago on a VM now doesn't so I'll just wait a bit for now.
|
galaxy/Chart.yaml
Outdated
condition: cvmfs.deploy | ||
alias: cvmfs | ||
tags: | ||
- deploy-cvmfs | ||
- name: rabbitmq-cluster-operator | ||
repository: https://charts.bitnami.com/bitnami | ||
version: 2.6.12 | ||
version: 4.3.22 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like there have been two major version changes. Have these changed the yaml configs in anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. These are the only notes I was able to find re. the release/upgrade process and nothing there seems to conflict with our setup: https://github.com/bitnami/charts/tree/main/bitnami/rabbitmq-cluster-operator#to-400
I launched 3 clusters with this version and ran a few IWC workflows, all of which worked as expected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Would outputs_to_working_directory
solve the permission issue that was encountered?
Good questions! I'll test it. |
I tested the updated deps on a K32 (1.30) cluster and worked as expected.
The outputs_to_working_directory option was a conclusion from a recent discussion.