> I'm glad that this has been potentially addressed in charmhelpers. I believe that all charms using apache2 will also need these fixes to address this
My assumption was that all of the OpenStack API charms inherit the Apache2 template in charm-helpers, but reactive charms don't. So I've made another review against charm-layer-openstack. https://bugs.launchpad.net/layer-openstack/+bug/1886630
> I'm glad that this has been potentially addressed in charmhelpers. I believe that all charms using apache2 will also need these fixes to address this
My assumption was that all of the OpenStack API charms inherit the Apache2 template in charm-helpers, but reactive charms don't. So I've made another review against charm-layer- openstack. /bugs.launchpad .net/layer- openstack/ +bug/1886630
https:/
OpenStack components which are not covered by those templates are: /opendev. org/openstack/ charm-openstack -dashboard/ commit/ e462df7401ac144 dce2aeb36b4e563 980410a920
- openstack dashboard as it's not an API endpoint, but WebUI
https:/
- VNC proxy as you and Xav mentioned
Agreed that it's good to scan all OpenStack charms if there is anything missing.