Skip to content
This repository has been archived by the owner on Oct 5, 2020. It is now read-only.

proxied runtime properties #134

Open
dfilppi opened this issue Apr 6, 2018 · 1 comment
Open

proxied runtime properties #134

dfilppi opened this issue Apr 6, 2018 · 1 comment

Comments

@dfilppi
Copy link

dfilppi commented Apr 6, 2018

Runtime properties are a bad idea when they are copies of any information that might change over time. This invites consistency problems. I suggest an enhancement to the DSL that allows the definition of runtime properties that are functions rather than simple map values (or some other scheme with the equivalent effect). This could be accomplished either with a dict subclass or a new API. Plugin defined types could define valid runtime properties (as required by TOSCA anyway), and in that definition be able to associate a plugin function or functions (essentially getters and setters).
This feature would be useful both for underlying Cloud providers, and also for "deployment proxy" types of scenarios. For example, rather than copying outputs from a target deployment, the deployment proxy would actually "proxy" the values in lazy fashion from the target deployment.

@dfilppi
Copy link
Author

dfilppi commented Apr 6, 2018

This is a feature idea. Github won't let me set a label

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant