Re: Catalog items - Plans vs Configs
Not entirely unrelated but the discrepancy between the plan/config caused a
problem that was them compounded because by the time I was able to inspect
the live model *stderr* had been garbage collected even though the item in
question was on fire.
If there is any issue deploying a blueprint garbage collecting the evidence
is the last thing Brooklyn should do.
On Tue, Jun 5, 2018 at 10:28 PM, Duncan Johnston-Watt <
> This is probably obvious to everyone else but when I inspect applications
> preloaded in a catalog I can see both a Plan and a Config associated with
> When I use +Application and select the catalog item corresponding to such
> an application I have two options -
> *Next (Wizard view)*
> Here the params are completed using the *Config* and unless I want to
> change them all I do at that point is select a location then deploy.
> *YAML Composer*
> Here I am presented with the *Plan* and have to add name/location etc. in
> the editor.
> Is this behaviour written up somewhere?
> Duncan Johnston-Watt
> CEO, Blockchain Technology Partners <http://blockchaintp.com/>
> Twitter: @duncanjw <https://twitter.com/duncanjw>
> Mob: +44 777 190 2653 <+44%207771%20902653>
> LinkedIn: https://linkedin.com/in/duncanjohnstonwatt
CEO, Blockchain Technology Partners <http://blockchaintp.com/>
Twitter: @duncanjw <https://twitter.com/duncanjw>
Mob: +44 777 190 2653 <+44%207771%20902653>