Implement Fn::Base64
Bug #1072955 reported by
Angus Salkeld
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Currently we don't actually encode anything in Base64 when Fn::Base64 appears in the template.
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in heat: | |
milestone: | none → grizzly-3 |
Changed in heat: | |
milestone: | grizzly-3 → none |
Changed in heat: | |
assignee: | Zane Bitter (zaneb) → Jeff Sloyer (jsloyer) |
Changed in heat: | |
assignee: | Jeff Sloyer (jsloyer) → Jun Jie Nan (nanjj) |
Changed in heat: | |
milestone: | none → icehouse-1 |
Changed in heat: | |
assignee: | Jun Jie Nan (nanjj) → nobody |
Changed in heat: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in heat: | |
status: | Triaged → Won't Fix |
milestone: | icehouse-3 → none |
To post a comment you must log in.
sdake
=====
I am pretty sure I tried this once and the userdata didn't end up in the virtual machine in a correct format. Feel free to give it another go tho :)
jeos tools show how to encode in b64. They encode the cfn tools.