ith
others. Having an option to hide default params from a shared actions would
have been handy. So a fine-grained control would help other use-cases too.
dragos
________
From: Rodric Rabbah
Sent: Wednesday, February 14, 2018 6:39:04 PM
To: dev@openwhisk.apache.org
Su
r use-cases too.
dragos
From: Rodric Rabbah
Sent: Wednesday, February 14, 2018 6:39:04 PM
To: dev@openwhisk.apache.org
Subject: Re: How to share an action but not its code, nor parameters
It’s worth mentioning that going through the web action path limits the
i've wanted, for a while now, the ability to encapsulate remote requests,
whether to other actions or to remote services, behind a Composer-like
linguistic facade.
so that, to sequence a call to any REST API, i would like to have, e.g.
composer.sequence('myOwnAction', composer.request({ url: '
ht
It’s worth mentioning that going through the web action path limits the
compositions to those that can complete is 60s. So there are other benefits to
pursuing the fine grained rights approach.
-r
> How would this work with Composer ?
composer.web(‘namespace/package/name’)
As an example. Olivier may have other ideas.
A combinator in composer is a programmable extension; so either adding
something specific to web actions or more generally a URL which can codegen
into an inline HTTP req
dnesday, February 14, 2018 6:10:47 PM
To: dev@openwhisk.apache.org
Subject: Re: How to share an action but not its code, nor parameters
The obvious path with composer is to create a combinator for invoking a URL,
which could treat web actions intrinsically.
This discussion has come up before - there’s also
The obvious path with composer is to create a combinator for invoking a URL,
which could treat web actions intrinsically.
This discussion has come up before - there’s also this related open issue on
the topic [1]. An alternative would be fine grained privileges on assets where
the default right
I think some openwhiskers have this use-case and I'm thinking to start a thread
to see what are the current options. and see if we can land a PR if we want to
support this use-case.
The need is to share an action with 3rd party developers, while retaining the
intellectual property of the code,
