DeWayne, I think you missed parts of this discussion where we answered some
these issues:
1) ARIA *does* allow you configure you choice of ID generation, and I agree
it can be an integration requirement. (We have a JIRA open to give this
configuration a CLI.)
2) ARIA has a choice of UUID formats
All,
This coming weekend (9/29) I plan to remove the roster sections from all
podling status pages.
Podling rosters are meant to be managed in Whimsy. The roster in the
status page is redundant and end up out of sync. In place of the roster, I
will be adding a link automatically to all podling
Hi
YAML1.0 spec is incorrect for import definitions.
YAML1.2 spec has updated the import grammar as follows.
It will be great for ARIA to support parts of the YAML1.2 spec soon especially
for areas that are corrected.
From YAML 1.2 spec:
3.5.8.2 Grammar
Import definitions have one the following
So, this is one of the cases where the spec seems to be wrong: the
is probably a mistake. None of the other examples in the spec
have it, nor do we see it in other TOSCA examples.
Note that if we needed an than it would even have to be for
the short form. So:
imports:
- importname1:
Hi Tal,
As per the grammer in the SPEC, seems the import should take a .
Your example dint have a but started with respository as such.
:
file:
repository:
namespace_uri:
namespace_prefix:
With your example can we have multiple repositories ?
Regards,
DJ
-Original
