RE: install_aria_extensions called twice

Hi, We have observed runtime error “Re-definition of YAML 1.1” error while executing the following service template. This happens when we define a complex type as input into an operation but the first entry must be an intrinsic function even if the type has been defined as string. We think it

install_aria_extensions called twice

Hi, We have observed that install_aria_extensions is called twice – once in process.py(executor) and once in main.py. Could you please confirm as to why it is called again in process.py? Regards, Srinidhi.

RE: get_attribute function not supporting SELF as

Hi, Yes this scenario is working fine. But in my case, I am not assigning default value to attribute in node type instead assigning the attribute value through a plugin(sample-1.0.0 in my case) using, ctx.node.attributes['config'] = "test" . Then I am trying to fetch this value through

Re: Jenkins job on ariatosca-website failing after gitbox transition

Jenkins is back up, and the website has been built. John On Tue, Dec 5, 2017 at 12:13 PM John D. Ament wrote: > Ok, so there's a couple of issues. > Jenkins access is limited to those in a certain group, since its a single > jenkins instance for all projects without

AriaTosca website published

The Apache Jenkins build system has built AriaTosca Website (build #38) Status: Successful Check console output at https://builds.apache.org/job/AriaTosca%20Website/38/ to view the results.

AriaTosca website published

The Apache Jenkins build system has built AriaTosca Website (build #37) Status: Fixed Check console output at https://builds.apache.org/job/AriaTosca%20Website/37/ to view the results.

Re: Jenkins job on ariatosca-website failing after gitbox transition

Ok, so there's a couple of issues. Jenkins access is limited to those in a certain group, since its a single jenkins instance for all projects without limited privileges. Right now I have access to manage jobs in jenkins, but would be happy to add others who need it. The jenkins job is something

Jenkins job on ariatosca-website failing after gitbox transition

i just realized that after the switch to gitbox, pushed PRs to the ariatosca-website repo are not triggering the Jenkins job which results in the site being re-generated and published to ariatosca.org [5:45] so my PR yesterday and @Miguel Jiménez’s from today while merged, are not yet reflected

AriaTosca website published

The Apache Jenkins build system has built AriaTosca Website (build #36) Status: Failure Check console output at https://builds.apache.org/job/AriaTosca%20Website/36/ to view the results.

Re: get_attribute function not supporting SELF as

Sure, it is seen below. I saved it as a file named "v.yaml" and then ran these commands to see the values of the function calls, which in both cases was "hello": aria service-templates store v.yaml v aria service-templates show v -f The file "v.yaml": tosca_definitions_version:

RE: get_attribute function not supporting SELF as

I have tried the same in the latest master version. Could you please provide the service template you used ? -Original Message- From: Tal Liron [mailto:t...@cloudify.co] Sent: Tuesday, December 05, 2017 3:41 PM To: dev@ariatosca.incubator.apache.org Subject: Re: get_attribute function not

Podling Report Reminder - December 2017

Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 December 2017, 10:30 am PDT. The report for your podling will

Subscribe for dev mailing list

Hi, Am looking for subscription for dev@ariatosca.incubator.apache.org to have my queries posted to dev forum. Could you help with this ? Regards, Vaishali

Re: Subscribe for dev mailing list

Email dev-subscr...@ariatosca.apache.org Sent from my iPhone > On Dec 5, 2017, at 12:48 AM, Vaishali Krishnamurthy > wrote: > > Hi, > > > > Am looking for subscription for dev@ariatosca.incubator.apache.org to have > my queries posted to dev forum.

Re: get_attribute function not supporting SELF as

I tried here and it did work for me. Are you using the latest master version? We had a few recent commits that have fixed various things. Perhaps you can provide a fully working minimal example that could clearly reproduce this bug? On Tue, Dec 5, 2017 at 12:02 PM, Vaishali Krishnamurthy <

RE: get_attribute function not supporting SELF as

Thanks. I tried this workaround. Still, the get_attribute function returns the value 'none' when used in the first level of inputs. In my case, I am trying to update the attribute value in one operation using plugin and fetch the updated attribute value in another operation using the get_attribute

Re: get_attribute function not supporting SELF as

The bug, in case you want to follow its progress: https://issues.apache.org/jira/browse/ARIA-424 On Tue, Dec 5, 2017 at 11:35 AM, Tal Liron wrote: > There is a bug here, but it has nothing to do with SELF. > > The issue is that you are using an "ad hoc", typeless input here

Re: get_attribute function not supporting SELF as

There is a bug here, but it has nothing to do with SELF. The issue is that you are using an "ad hoc", typeless input here for the "configure" operation. Because it's typeless, ARIA sends it "as is" and thus has no idea that what's inside might be a syntactical intrinsic function. I will open a

RE: get_attribute function not supporting SELF as

Here, I have used the get_attribute in the input defined in the second level, for which it returns me the dictionary object. inputs: payload: { "config": {get_attribute: [ SELF, vmme_configuration ]}} When I use the get_attribute in inputs defined in the first level it returns

Re: get_attribute function not supporting SELF as

Thanks for the report. Do you possibly have a minimal TOSCA template we can use to reproduce the error? On Tue, Dec 5, 2017 at 8:29 AM, Vaishali Krishnamurthy < v.krishnamurt...@globallogic.com.invalid> wrote: > Hi, > > We have observed the attribute resolution is not proper when we use SELF as