Both the cinder and glance charms are in the middle of a python rewrite and I'd prefer to include the proper solution as part of that work. Since we both agree the solution should exist in the image-service relation interface, I'd prefer not to add temporary config options to config.yaml as a stop-gap.
One alternative solution for the short-term that comes to mind is implementing a 'config-flags' field in cinder similar to the nova-* that let you define arbitrary key=value settings that get set in config. This would let you set the flag (and any others) until the interface supports handling it for you.
Hey Edward-
Both the cinder and glance charms are in the middle of a python rewrite and I'd prefer to include the proper solution as part of that work. Since we both agree the solution should exist in the image-service relation interface, I'd prefer not to add temporary config options to config.yaml as a stop-gap.
One alternative solution for the short-term that comes to mind is implementing a 'config-flags' field in cinder similar to the nova-* that let you define arbitrary key=value settings that get set in config. This would let you set the flag (and any others) until the interface supports handling it for you.