Re: install_aria_extensions called twice

; srinidhi.srivat...@globallogic.com.INVALID] > Sent: Friday, December 08, 2017 11:32 AM > To: dev@ariatosca.incubator.apache.org > Subject: RE: install_aria_extensions called twice > > Hi, > > Thanks for the information. Will this item be prioritized and fixed? > > Regards, >

Re: [VOTE] publish ariatosca 0.2.0

1. Validated signature & checksums 2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3. Ran RAT check 4. Made a clean install using "pip install ." 5. Ran tests using "make test" +1 On Thu, Jan 4, 2018 at 5:59 PM Thomas Nadeau wrote: > Aria

Re: Database session management with model storage.

es in session management to > effectively support multithreading scenarios. > If all agree we can contribute on this. > > Regards, > DJ > -Original Message- > From: D Jayachandran > Sent: Friday, December 29, 2017 12:01 PM > To: dev@ariatosca.incubator.apache.org; Maxi

Re: install_aria_extensions called twice

The removal on the call to install_aria_extensions does solve the problem in your case, however this might raise other issue. For example: writing a process executor extension would have no effect if you'd remove the `install_aria_extensions` function call. The actual problem is caused because

Making the usage of ARIA more generic

I've been working on making the usage of ARIA more generic, and opened up a few PRS: - https://github.com/apache/incubator-ariatosca/pull/209 - making the update of tasks triggered by events more generic. - https://github.com/apache/incubator-ariatosca/pull/211 - the current json

Re: problem using cloudify extension with dev branch

The extension repo was built based on Aria 0.1.1 base code. The dependency is strictly set to 0.1.1 , which kinda make sense since 0.2.0 wasn't (and still isn't) released. It probably uninstalls the 0.2.0 one and installs 0.1.1 instead, which sound to me as a wanted behavior. On Thu, Nov 30,

Re: Official Project Vote: Moving to Gitbox

+1 On Wed, Nov 8, 2017 at 7:41 PM Vishwanath Jayaraman wrote: > +1 > > Sent from my iPhone > > On Nov 8, 2017, at 10:25 AM, Suneel Marthi > wrote: > > +1 > > Sent from my iPhone > > On Nov 8, 2017, at 9:52 PM,

Re: TOSCA spec compliance on finding target node

The support for satisfying a requirement according to a capability type was just added as part of https://github.com/apache/incubator-ariatosca/commit/df2b916e624719e5f77e29c1e893c55f88e15862 On Mon, Aug 7, 2017 at 6:30 PM, Tal Liron wrote: > I think you are talking about

Re: Inputs and Node object context for python and shell scripts

collections. > > Regards, > DJ > -Original Message- > From: Maxim Orlov [mailto:ma...@cloudify.co] > Sent: Tuesday, August 01, 2017 4:24 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Inputs and Node object context for python and shell scripts > > Sor

Re: Inputs and Node object context for python and shell scripts

" On Tue, Aug 1, 2017 at 1:48 PM Maxim Orlov <ma...@cloudify.co> wrote: > Oh, i see. For each method which represents an operation, you should use > the @operation decorator. Thus samplemethod would look like this: > > from aria import operation > @operation > >

Re: Inputs and Node object context for python and shell scripts

> labels: > type: string > required: false > default: test > isService: > type: boolean > required: false >

Re: Inputs and Node object context for python and shell scripts

as like a dict. It > seems to fail when it tries to remove the existing value and triggering a > change event. > > ObjectDereferencedError: Can't emit change event for attribute > 'Node.attributes' - parent object of type has been garbage collected > > > Regards, > DJ > >

Re: Inputs and Node object context for python and shell scripts

e ) > > ctx.node.attributes['test'].value > > And to update the value > > ctx.node.attributes['test'].value = "abc" > > But this does not update the db. Am I missing something here in-terms of > the context usage ? > > > Regards, > DJ > -Original Mess

Re: Inputs and Node object context for python and shell scripts

Sorry it took me so long to check it out, things have been kind of hectic. Anyway, there is a JIRA issue opened just for that: https://issues.apache.org/jira/browse/ARIA-263. On Tue, Jul 25, 2017 at 9:23 PM, Maxim Orlov <ma...@cloudify.co> wrote: > Not entirely sure about that actuall

Re: Openstack plugin

standing ? Also why this adapter is not included > with ARIA by default ? > > > Regards, > DJ > -Original Message- > From: Maxim Orlov [mailto:ma...@gigaspaces.com] > Sent: Monday, July 24, 2017 9:17 PM > To: dev@ariatosca.incubator.apache.org > Subject:

Re: Unique identification of an instance element across services

tps://github.com/wyattisimo/base57-ruby On Tue, Jul 25, 2017 at 1:28 PM, Maxim Orlov <ma...@cloudify.co> wrote: > Actually the refactoring was made so the id would be more user readable. > The index is determined according to the used indices (it's not just a > running number). If indeed th

Re: Unique identification of an instance element across services

Actually the refactoring was made so the id would be more user readable. The index is determined according to the used indices (it's not just a running number). If indeed this poses an issue (or if indeed a uuid is easier to recognize, or even use in a query), let's discuss it further... On Tue,

Re: Inputs and Node object context for python and shell scripts

? > > On Tue, Jul 25, 2017 at 7:33 AM, Maxim Orlov <ma...@cloudify.co> wrote: > > > Indeed runtime_properties became attributes in ARIA . As for the > behavior, > > attributes behave just as a dict would (behind the scenes attributes > > translate to a prop

Re: Inputs and Node object context for python and shell scripts

;globals". I will re-confirm this. > The inputs which I was referring here were the lifecycle operation inputs. > > > Regards, > DJ > > -Original Message- > From: Maxim Orlov [mailto:ma...@gigaspaces.com] > Sent: Tuesday, July 25, 2017 12:14 AM > To: dev@ariat

Re: Inputs and Node object context for python and shell scripts

I'm not entirely sure to which inputs you are referring to, but any ctx attribute or method accessible from a python script is accessible form any shell script. For example: - "ctx.node.attributes['map']['key']" (in python) is "ctx node attributes map.key" (under bash) -

Re: Openstack plugin

Hey DJ, Basically ARIA indeed has an adapter for cloudify-based plugins. This enables support for any cloudify plugins (Provided the plugin.yaml has been translated into TOSCA). Note that later on, ARIA will have native plugins and will not rely on kindness of Cloudify. You can find the Cloudify

Re: async execution/task management

However, note that since each process creates its own workflow_runner (and consequently a new engine), starting and ending the workflow_runner should be done from the same process. On Thu, Jul 13, 2017 at 11:39 AM Maxim Orlov <ma...@gigaspaces.com> wrote: > The execution id is indeed th

Re: async execution/task management

The execution id is indeed the linking factor between all execution related operations. ARIA doesn't provide asynchronous execution based operations. However, here you can see how ARIA runs executions

Re: [VOTE] publish ariatosca 0.1.1

1. Validated signature & checksums 2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3. Ran RAT check 4. Made a clean install using "pip install ." 5. Ran tests using "make test" +1 On Tue, Jul 11, 2017 at 2:27 AM, Suneel Marthi wrote: > +1

Re: How can I use aria CLI options correctly?

In order to get a more detailed message, you could use the verbosity flag - "-v". This flag is supported both for the execution start command and the logs list command. What you would want to do at this stage is try and figure out what happend with the execution you already ran. In order to do

Re: [UPDATE] Work on ARIA-149: Support intrinsic functions in "dependencies" operation configuration

Not entirely sure why the "implementation" gets its own field. It basically another input to the operation. Though it's a special input (since it enables for the plugin do decide which "function" to run), it's still an inputs. feel we already have a lot of different possible inputs to an

[jira] [Created] (ARIA-248) When applying tracked changes fails no message is returned

Maxim Orlov created ARIA-248: Summary: When applying tracked changes fails no message is returned Key: ARIA-248 URL: https://issues.apache.org/jira/browse/ARIA-248 Project: AriaTosca Issue Type

[jira] [Resolved] (ARIA-160) Operation toolbelt unit tests fail spordically

[ https://issues.apache.org/jira/browse/ARIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov resolved ARIA-160. -- Resolution: Fixed > Operation toolbelt unit tests fail spordica

[jira] [Resolved] (ARIA-165) Make node name suffix UUIDs become more readable

[ https://issues.apache.org/jira/browse/ARIA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov resolved ARIA-165. -- Resolution: Fixed Fix Version/s: 0.1.0 > Make node name suffix UUIDs become more reada

[jira] [Resolved] (ARIA-230) Dry execution doesn't log empty operations

[ https://issues.apache.org/jira/browse/ARIA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov resolved ARIA-230. -- Resolution: Fixed Fix Version/s: 0.1.0 > Dry execution doesn't log empty operati

[jira] [Reopened] (ARIA-160) Operation toolbelt unit tests fail spordically

[ https://issues.apache.org/jira/browse/ARIA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov reopened ARIA-160: -- > Operation toolbelt unit tests fail spordica

[jira] [Created] (ARIA-230) Dry execution doesn't log empty operations

Maxim Orlov created ARIA-230: Summary: Dry execution doesn't log empty operations Key: ARIA-230 URL: https://issues.apache.org/jira/browse/ARIA-230 Project: AriaTosca Issue Type: Bug Affects

[jira] [Commented] (ARIA-165) Make node name suffix UUIDs become more readable

[ https://issues.apache.org/jira/browse/ARIA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000785#comment-16000785 ] Maxim Orlov commented on ARIA-165: -- We can uitilze the SQLAlcehmy events mechanism, which could automate

[jira] [Closed] (ARIA-214) Dry execution changes the state of non implemented operations

[ https://issues.apache.org/jira/browse/ARIA-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-214. Resolution: Fixed Fix Version/s: 0.1.0 > Dry execution changes the state of non implemented operati

[jira] [Updated] (ARIA-214) Dry execution changes the state of non implemented operations

[ https://issues.apache.org/jira/browse/ARIA-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-214: - Summary: Dry execution changes the state of non implemented operations (was: Dry execution still change

[jira] [Created] (ARIA-214) Dry execution still change the state of non implemented operations

Maxim Orlov created ARIA-214: Summary: Dry execution still change the state of non implemented operations Key: ARIA-214 URL: https://issues.apache.org/jira/browse/ARIA-214 Project: AriaTosca

[jira] [Assigned] (ARIA-165) Make node name suffix UUIDs become more readable

[ https://issues.apache.org/jira/browse/ARIA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov reassigned ARIA-165: Assignee: Maxim Orlov > Make node name suffix UUIDs become more reada

[jira] [Closed] (ARIA-163) Update node state for stub tasks

[ https://issues.apache.org/jira/browse/ARIA-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-163. Resolution: Fixed Fix Version/s: 0.1.0 > Update node state for stub ta

[jira] [Created] (ARIA-208) Missing backref for models

Maxim Orlov created ARIA-208: Summary: Missing backref for models Key: ARIA-208 URL: https://issues.apache.org/jira/browse/ARIA-208 Project: AriaTosca Issue Type: Bug Reporter: Maxim

[jira] [Created] (ARIA-163) Update node state for stub tasks

Maxim Orlov created ARIA-163: Summary: Update node state for stub tasks Key: ARIA-163 URL: https://issues.apache.org/jira/browse/ARIA-163 Project: AriaTosca Issue Type: Story Affects

[jira] [Closed] (ARIA-147) Support auto-completion in CLI

[ https://issues.apache.org/jira/browse/ARIA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-147. Resolution: Fixed Fix Version/s: 0.1.0 The current auto-completion supports only static bash

[jira] [Closed] (ARIA-158) Restore support for relationship ordering

[ https://issues.apache.org/jira/browse/ARIA-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-158. Resolution: Fixed Fix Version/s: 0.1.0 > Restore support for relationship order

[jira] [Closed] (ARIA-152) Openstack hello-world example

[ https://issues.apache.org/jira/browse/ARIA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-152. Resolution: Fixed Fix Version/s: 0.1.0 > Openstack hello-world exam

[jira] [Comment Edited] (ARIA-147) Support auto-completion in CLI

[ https://issues.apache.org/jira/browse/ARIA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980495#comment-15980495 ] Maxim Orlov edited comment on ARIA-147 at 4/24/17 9:34 AM: --- The commands auto

[jira] [Comment Edited] (ARIA-147) Support auto-completion in CLI

[ https://issues.apache.org/jira/browse/ARIA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980495#comment-15980495 ] Maxim Orlov edited comment on ARIA-147 at 4/23/17 6:11 PM: --- The commands auto

[jira] [Commented] (ARIA-147) Support auto-completion in CLI

[ https://issues.apache.org/jira/browse/ARIA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980495#comment-15980495 ] Maxim Orlov commented on ARIA-147: -- The commands auto completion is a builtin click feature. to activate

[jira] [Comment Edited] (ARIA-147) Support auto-completion in CLI

[ https://issues.apache.org/jira/browse/ARIA-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980495#comment-15980495 ] Maxim Orlov edited comment on ARIA-147 at 4/23/17 6:10 PM: --- The commands auto

[jira] [Created] (ARIA-144) sql_mapi raises an error in regards to date_time string

Maxim Orlov created ARIA-144: Summary: sql_mapi raises an error in regards to date_time string Key: ARIA-144 URL: https://issues.apache.org/jira/browse/ARIA-144 Project: AriaTosca Issue Type

[jira] [Closed] (ARIA-142) defaults missing for execution plugin

[ https://issues.apache.org/jira/browse/ARIA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-142. Resolution: Fixed > defaults missing for execution plu

[jira] [Created] (ARIA-142) defaults missing for execution plugin

Maxim Orlov created ARIA-142: Summary: defaults missing for execution plugin Key: ARIA-142 URL: https://issues.apache.org/jira/browse/ARIA-142 Project: AriaTosca Issue Type: Bug Affects

[jira] [Deleted] (ARIA-141) Implementation-less relationship tasks are being created.

[ https://issues.apache.org/jira/browse/ARIA-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov deleted ARIA-141: - > Implementation-less relationship tasks are being crea

[jira] [Closed] (ARIA-137) Support for predicate based queries in the SQL mapi

[ https://issues.apache.org/jira/browse/ARIA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-137. Resolution: Fixed Fix Version/s: 0.1.0 > Support for predicate based queries in the SQL m

[jira] [Closed] (ARIA-136) ctx binary doesn't get installed via pip install

[ https://issues.apache.org/jira/browse/ARIA-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-136. Resolution: Fixed Fix Version/s: 0.1.0 > ctx binary doesn't get installed via pip inst

[jira] [Assigned] (ARIA-136) ctx binary doesn't get installed via pip install

[ https://issues.apache.org/jira/browse/ARIA-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov reassigned ARIA-136: Assignee: Maxim Orlov > ctx binary doesn't get installed via pip inst

[jira] [Closed] (ARIA-125) Filtering returns the wrong models

[ https://issues.apache.org/jira/browse/ARIA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-125. Resolution: Fixed Fix Version/s: 0.1.0 > Filtering returns the wrong mod

[jira] [Closed] (ARIA-86) Create a basic "Hello World" blueprint example

[ https://issues.apache.org/jira/browse/ARIA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-86. --- Resolution: Fixed > Create a basic "Hello World" blue

[jira] [Updated] (ARIA-135) Add plugin field to MockTask

[ https://issues.apache.org/jira/browse/ARIA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-135: - Summary: Add plugin field to MockTask (was: Add plugin field to MockContext) > Add plugin fi

[jira] [Created] (ARIA-135) Add plugin field to MockContext

Maxim Orlov created ARIA-135: Summary: Add plugin field to MockContext Key: ARIA-135 URL: https://issues.apache.org/jira/browse/ARIA-135 Project: AriaTosca Issue Type: Task Reporter

[jira] [Closed] (ARIA-120) Builtin workflows have wrong execution order in relationship operations

[ https://issues.apache.org/jira/browse/ARIA-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIA-120. Resolution: Fixed Assignee: Maxim Orlov Fix Version/s: 0.1.0 > Builtin workflows have wr

[jira] [Created] (ARIA-131) Make demand for networkx more strict

Maxim Orlov created ARIA-131: Summary: Make demand for networkx more strict Key: ARIA-131 URL: https://issues.apache.org/jira/browse/ARIA-131 Project: AriaTosca Issue Type: Bug Affects

[jira] [Created] (ARIA-130) Passing inputs from the workflow to the operation changes the inputs

Maxim Orlov created ARIA-130: Summary: Passing inputs from the workflow to the operation changes the inputs Key: ARIA-130 URL: https://issues.apache.org/jira/browse/ARIA-130 Project: AriaTosca

[jira] [Created] (ARIA-125) Filtering returns the wrong models

Maxim Orlov created ARIA-125: Summary: Filtering returns the wrong models Key: ARIA-125 URL: https://issues.apache.org/jira/browse/ARIA-125 Project: AriaTosca Issue Type: Bug Affects

[jira] [Updated] (ARIA-122) Create central instantiation module

[ https://issues.apache.org/jira/browse/ARIA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-122: - Summary: Create central instantiation module (was: Createe central instantiation module) > Create cent

[jira] [Created] (ARIA-122) Createe central instantiation module

Maxim Orlov created ARIA-122: Summary: Createe central instantiation module Key: ARIA-122 URL: https://issues.apache.org/jira/browse/ARIA-122 Project: AriaTosca Issue Type: Bug

[jira] [Created] (ARIA-117) Log model should have an Execution field

Maxim Orlov created ARIA-117: Summary: Log model should have an Execution field Key: ARIA-117 URL: https://issues.apache.org/jira/browse/ARIA-117 Project: AriaTosca Issue Type: Task

[jira] [Created] (ARIA-116) Missing type_hierarchy in relationship

Maxim Orlov created ARIA-116: Summary: Missing type_hierarchy in relationship Key: ARIA-116 URL: https://issues.apache.org/jira/browse/ARIA-116 Project: AriaTosca Issue Type: Bug Affects

[jira] [Created] (ARIA-109) Updating tracked changes should persist

Maxim Orlov created ARIA-109: Summary: Updating tracked changes should persist Key: ARIA-109 URL: https://issues.apache.org/jira/browse/ARIA-109 Project: AriaTosca Issue Type: Story Affects

[jira] [Updated] (ARIA-106) Create sqla logging handler

[ https://issues.apache.org/jira/browse/ARIA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-106: - Description: Create an sql based logging mechanism for operations and workflows. > Create sqla logg

[jira] [Created] (ARIA-95) pip wheel for aria ignores dependencies

Maxim Orlov created ARIA-95: --- Summary: pip wheel for aria ignores dependencies Key: ARIA-95 URL: https://issues.apache.org/jira/browse/ARIA-95 Project: AriaTosca Issue Type: Bug Affects

[jira] [Created] (ARIA-66) Convert custom parser fields into sqla based fields

Maxim Orlov created ARIA-66: --- Summary: Convert custom parser fields into sqla based fields Key: ARIA-66 URL: https://issues.apache.org/jira/browse/ARIA-66 Project: AriaTosca Issue Type: Sub-task

[jira] [Created] (ARIA-58) Storage model to_dict creates symbolic links

Maxim Orlov created ARIA-58: --- Summary: Storage model to_dict creates symbolic links Key: ARIA-58 URL: https://issues.apache.org/jira/browse/ARIA-58 Project: AriaTosca Issue Type: Bug Affects

[jira] [Created] (ARIA-57) Custom executions state transition support

Maxim Orlov created ARIA-57: --- Summary: Custom executions state transition support Key: ARIA-57 URL: https://issues.apache.org/jira/browse/ARIA-57 Project: AriaTosca Issue Type: Story Affects

[jira] [Updated] (ARIA-52) Support order management in relationships

[ https://issues.apache.org/jira/browse/ARIA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-52: Summary: Support order management in relationships (was: Support-order-management-in-relationships

[jira] [Created] (ARIA-52) Support-order-management-in-relationships

Maxim Orlov created ARIA-52: --- Summary: Support-order-management-in-relationships Key: ARIA-52 URL: https://issues.apache.org/jira/browse/ARIA-52 Project: AriaTosca Issue Type: Bug

[jira] [Created] (ARIATOSCA-39) Genericize storage models

Maxim Orlov created ARIATOSCA-39: Summary: Genericize storage models Key: ARIATOSCA-39 URL: https://issues.apache.org/jira/browse/ARIATOSCA-39 Project: AriaTosca Issue Type: Story

[jira] [Closed] (ARIATOSCA-30) SQL base storage implementation

[ https://issues.apache.org/jira/browse/ARIATOSCA-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-30. Resolution: Fixed Fix Version/s: 0.1.0 > SQL base storage implementat

[jira] [Closed] (ARIATOSCA-25) Storage genericizing

[ https://issues.apache.org/jira/browse/ARIATOSCA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-25. Resolution: Won't Fix This is no longer relevant, as the storage has new architecture. > Stor

[jira] [Closed] (ARIATOSCA-21) Reorder repository strucutre

[ https://issues.apache.org/jira/browse/ARIATOSCA-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-21. Resolution: Fixed Fix Version/s: 0.1.0 > Reorder repository strucu

[jira] [Closed] (ARIATOSCA-8) API for workflow context

[ https://issues.apache.org/jira/browse/ARIATOSCA-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-8. --- Resolution: Fixed Fix Version/s: 0.1.0 > API for workflow cont

[jira] [Reopened] (ARIATOSCA-12) API for executing workflows

[ https://issues.apache.org/jira/browse/ARIATOSCA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov reopened ARIATOSCA-12: -- Assignee: (was: Maxim Orlov) > API for executing workfl

[jira] [Closed] (ARIATOSCA-12) API for executing workflows

[ https://issues.apache.org/jira/browse/ARIATOSCA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-12. Resolution: Fixed Fix Version/s: 0.1.0 > API for executing workfl

[jira] [Closed] (ARIATOSCA-9) API for operation context

[ https://issues.apache.org/jira/browse/ARIATOSCA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-9. --- Resolution: Fixed Fix Version/s: 0.1.0 > API for operation cont

Re: JIRA configuration changes

+1 good points, could be really helpful On Mon, Nov 14, 2016 at 10:58 PM, Avia Efrat wrote: > Overall, Ran's suggestions go well with my vision of the development > process. > I just want to further emphasize, the less options and fields in a Jira > issue screen (as long as

[jira] [Closed] (ARIATOSCA-5) Adapt workflow API uses to the modified API

[ https://issues.apache.org/jira/browse/ARIATOSCA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-5. --- Resolution: Fixed Fix Version/s: 0.1.0 > Adapt workflow API uses to the modified

[jira] [Closed] (ARIATOSCA-3) API for creating workflows

[ https://issues.apache.org/jira/browse/ARIATOSCA-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov closed ARIATOSCA-3. --- Resolution: Fixed Fix Version/s: 0.1.0 > API for creating workfl

[jira] [Updated] (ARIATOSCA-5) Adapt workflow API uses to the modified API

[ https://issues.apache.org/jira/browse/ARIATOSCA-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIATOSCA-5: Summary: Adapt workflow API uses to the modified API (was: Adapt workflow API users

[jira] [Assigned] (ARIATOSCA-9) API for operation context

[ https://issues.apache.org/jira/browse/ARIATOSCA-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov reassigned ARIATOSCA-9: --- Assignee: Maxim Orlov > API for operation cont