vault-charm

add more granularity to reissue-certificates action

Bug #1960646 reported by Garrett Neugent
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
vault-charm
Triaged
Wishlist
Unassigned

Bug Description

Currently, the reissue-certificates action defaults to reissuing certs for all applications that are related to vault. Instead, it would be great if the operator could to pass a list for specifying which applications, so there is more control, e.g:

juju run-action vault/leader reissue-certificates apps=aodh,openstack-dashboard,nagios

If this is adopted, it would be great to also have an `--all` flag, to handle the intended cases where all applications need a new certificate.

Thanks for your time!

Revision history for this message
Billy Olsen (billy-olsen) wrote :

This will be a bit tricky to implement, especially for any models which are in a cross-model relation as the remote application name is not necessarily known to Vault, so the user experience will be confusing.

I agree that this would be a good feature to implement, but will need to review possible options of what might work here.

Changed in vault-charm:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.