Thank you for your work on this. It seems like a large enough feature proposal that a feature spec and implementation conversations are in order.
There are potential security and data accessibility implications, and I want to make sure this is implemented with core charmer design review and acceptance.
Please review the following information and spark the conversations as referenced.
That process will inherently flush out some of the other concerns that I have here, which are: unit test and functional test coverage of the newly-introduced charm feature.
Thank you for your work on this. It seems like a large enough feature proposal that a feature spec and implementation conversations are in order.
There are potential security and data accessibility implications, and I want to make sure this is implemented with core charmer design review and acceptance.
Please review the following information and spark the conversations as referenced.
https:/ /docs.openstack .org/charm- guide/latest/ feature- specification. html /docs.openstack .org/charm- guide/latest/ how-to- contribute. html
https:/
That process will inherently flush out some of the other concerns that I have here, which are: unit test and functional test coverage of the newly-introduced charm feature.
Thanks again.