Hi,
In addition to that we have to specify in cartridge json which metadata it
expose . For instance MySQL cartridge should mention that it exposes host,
username,password so someone looking at MySQL cartridge know what details
it exposes to metadata service.
exportingProperties{
[
"H
Hi,
Thanks Isuru for the suggestion.
On Sun, Oct 5, 2014 at 1:41 PM, Gayan Gunarathne wrote:
> +1
> Yeah I think it should be a json array.
> IMO we can use mygroup1.mygroup1mysql1 sort of a naming for identify the
> dendencies as it improves the readability of the alias.WDYT?
>
> Thanks,
> Gay
+1
Yeah I think it should be a json array.
IMO we can use mygroup1.mygroup1mysql1 sort of a naming for identify the
dendencies as it improves the readability of the alias.WDYT?
Thanks,
Gayan
On Friday, October 3, 2014, Isuru Haththotuwa wrote:
> +1 for the general idea, can we come up with the
+1 for the general idea, can we come up with the better name for
'metaInfoAlias'? Just my opinion, it seems misleading to me. How about
'dependencyAliases' ? And note that it should actually be an array, since
there can be a one-to-many relationship.
On Fri, Oct 3, 2014 at 3:32 PM, Udara Liyanage
Hi,
According to the new metadata services usage, some instances send its
details to the metadata service so interested parties can retrive the
details from the metadata service. Party which gets the details should know
from which details it needs to retrive. For instance, PHP should get
details p
