Heat encryption-key write-once

Bug #1732175 reported by Peter Sabaini
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat Charm
Triaged
Low
Unassigned

Bug Description

From reading the hooks it appears that encryption-key is a write-once value, ie. once set, cannot be updated (cf. heat_context.get_encryption_key())

This should be documented and/or be caught in the call to config-changed

Ver: 17.02

Revision history for this message
James Page (james-page) wrote :

Agreed

tags: added: ux
Changed in charm-heat:
status: New → Triaged
importance: Undecided → Low
milestone: none → 18.02
Ryan Beisner (1chb1n)
Changed in charm-heat:
milestone: 18.02 → 18.05
James Page (james-page)
Changed in charm-heat:
milestone: 18.05 → 18.08
James Page (james-page)
Changed in charm-heat:
milestone: 18.08 → 18.11
James Page (james-page)
Changed in charm-heat:
milestone: 18.11 → 19.04
David Ames (thedac)
Changed in charm-heat:
milestone: 19.04 → 19.07
David Ames (thedac)
Changed in charm-heat:
milestone: 19.07 → 19.10
David Ames (thedac)
Changed in charm-heat:
milestone: 19.10 → 20.01
James Page (james-page)
Changed in charm-heat:
milestone: 20.01 → 20.05
David Ames (thedac)
Changed in charm-heat:
milestone: 20.05 → 20.08
James Page (james-page)
Changed in charm-heat:
milestone: 20.08 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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