You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Chris Lambert (JIRA)" <ji...@apache.org> on 2014/06/02 21:41:03 UTC
[jira] [Updated] (AURORA-496) Modify config binding helper
registration in clientv2
[ https://issues.apache.org/jira/browse/AURORA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Lambert updated AURORA-496:
---------------------------------
Sprint: Q2 Sprint 2, Q2 Sprint 3 (was: Q2 Sprint 2)
> Modify config binding helper registration in clientv2
> -----------------------------------------------------
>
> Key: AURORA-496
> URL: https://issues.apache.org/jira/browse/AURORA-496
> Project: Aurora
> Issue Type: Task
> Components: Client
> Reporter: Mark Chu-Carroll
> Assignee: Mark Chu-Carroll
>
> Config binding helpers (components that add macros to the pystachio
> config language) were registered in a way that used self-construction.
> In practice, binding helpers need initialization that comes from command-line parameters. With the implicit construction method, we can't provide construction parameters to the helpers.
> We need to switches to an explicit construction/registration, instead
> of auto-construction when the class is registered. (Interestingly, this
> is the way that the documentation on the binding helpers code says that
> it works!)
> Instead of writing:
> FooHelper.register()
> We should write:
> BindingHelper.register(FooHelper())
> Which makes it possible to do:
> BindingHelper.register(FooHelper(url=bar))
--
This message was sent by Atlassian JIRA
(v6.2#6252)