cf-charmers team mailing list archive

[prismakov@xxxxxxxxx]

Cory, thank you for the answer. Refactoring etcd, my-sql-broker.

- A.P. | Altoros

On May 30, 2014, at 16:18, Cory Johns <cory.johns@xxxxxxxxxxxxx> wrote:

> Alex P.
> 
> The services framework has been refactored to no longer require
> StaticContext nor ConfigContext.  You can now simply use a regular
> dict() and add the result of hookenv.config() directly into the the
> "required_data" list (which is analogous to the old "contexts" list).
> There are examples in the CF charms trunk, and the docstrings for the
> classes and methods in charmhelpers.core.services are quite complete.
> 
> Note that there was a significant change in concept, from being
> focused on generating templates, to being a general framework for
> describing what data is needed to complete the setup and what to do
> when that data is available.  But, in practice, that mostly translates
> into a few keys changing in the service definition, the reduction in
> simple wrapper Context classes, as you noted, and having a general way
> of attaching callbacks to handle the work that has to happen when
> finalizing the setup of a service.
> 
> On Fri, May 30, 2014 at 4:07 AM,  <prismakov@xxxxxxxxx> wrote:
>> Hi Cory, guys
>> 
>> Where to find charm helpers which are ready to use in CF charms development?
>> 
>> E.g.
>> 
>> lp:~cf-charmers/charm-helpers/cloud-foundry
>> 
>> doesn’t contain Static(Config)Context. Or I missed something?
>> 
>> -Alex P. | Altoros