Heat encryption-key write-once

Bug #1732175 reported by Peter Sabaini on 2017-11-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack heat charm
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) on 2018-03-09
Changed in charm-heat:
milestone: 18.02 → 18.05
James Page (james-page) on 2018-06-12
Changed in charm-heat:
milestone: 18.05 → 18.08
James Page (james-page) on 2018-09-12
Changed in charm-heat:
milestone: 18.08 → 18.11
James Page (james-page) on 2018-11-20
Changed in charm-heat:
milestone: 18.11 → 19.04
David Ames (thedac) on 2019-04-17
Changed in charm-heat:
milestone: 19.04 → 19.07
David Ames (thedac) on 2019-08-12
Changed in charm-heat:
milestone: 19.07 → 19.10
David Ames (thedac) on 2019-10-24
Changed in charm-heat:
milestone: 19.10 → 20.01
James Page (james-page) on 2020-03-02
Changed in charm-heat:
milestone: 20.01 → 20.05
David Ames (thedac) on 2020-05-21
Changed in charm-heat:
milestone: 20.05 → 20.08
James Page (james-page) on 2020-08-03
Changed in charm-heat:
milestone: 20.08 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers