openstack/charm-vault
Code Issues Proposed changes

auto-unlock: make things clear about security

Browse Source 
Rename auto-unlock configuration option to make things clear to
CLI users that this really is a totally unsecure deployment
option!

Change-Id: I47726c65698bea1c35766d5c3ef16befad8ec72d
This commit is contained in:
James Page
2018-05-08 14:34:54 +01:00
parent 28fb89a44b
commit dbbf4d9a09
4 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/reactive/vault_handlers.py
View File

@@ -136,7 +136,7 @@ def snap_refresh():
if vault.can_restart():
log("Restarting vault", level=DEBUG)
service_restart('vault')
if config('auto-unlock'):
if config('totally-unsecure-auto-unlock'):
vault.prepare_vault()
else:
set_flag('snap.channel.invalid')
@@ -365,7 +365,7 @@ def cluster_connected(hacluster):
def file_change_auto_unlock_mode():
log("Calling opportunistic_restart", level=DEBUG)
vault.opportunistic_restart()
if config('auto-unlock'):
if config('totally-unsecure-auto-unlock'):
vault.prepare_vault()