Allow JSON values for parameters

Registered by Steven Hardy on 2013-05-01

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Randall Burt
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Randall Burt on 2013-06-19
Completed by
Randall Burt on 2013-06-26

Related branches

Sprints

Whiteboard

In order to pass e.g. resource metadata to a nested stack as a parameter, we need to have a parameter type that accepts JSON objects instead of just strings.

(asalkeld) I am not convinced this is the right approach.

(randallburt) asalkeld: wouldn't you lose the ability to pass resource metadata scripts and cloud-config stuff as parameters? Or do you propose we treat them as any other string param and do the work inside the template resource class?

(asalkeld) randall after thinking about this I can't think of a better way, so I guess this is it. It's just a matter of fitting a square (resource) into a circle (stack).

(thomas-spatzier) Just to verify: is related to the provider resource discussions? I.e. assuming we have a provider for some type of resource, and that provider (the implementation) needs and understands complex data structions (json object instead of simple string), we want to be able to pass this along?

Gerrit topic: https://review.openstack.org/#q,topic:bp/json-parameters,n,z

Addressed by: https://review.openstack.org/33572
    Allow JSON values for parameters

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.