Re: Catalog items - Plans vs Configs
Thanks. I followed the document link you suggested but when I clicked on
the embedded Catalog link I discovered that this was broken. Maybe to
Tool tips for "YAML Composer" and "Next" (Wizard) could be more specific in
terms of where they get parameters from?
On Thu, Jun 7, 2018 at 9:49 AM, Geoff Macartney <
> Hi Duncan
> there is some documentation at , but maybe not enough detail.
> I have raised the issue  to do something about this.
>  https://issues.apache.org/jira/browse/BROOKLYN-591
> On Tue, 5 Jun 2018 at 22:28 Duncan Johnston-Watt <duncan@xxxxxxxxxxxxxxxx>
> > 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
> > them.
> > 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?
> > Best
> > --
> > Duncan Johnston-Watt
> > CEO, Blockchain Technology Partners <http://blockchaintp.com/>
> > Twitter: @duncanjw <https://twitter.com/duncanjw>
> > Mob: +44 777 190 2653 <+44%207771%20902653> <+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>