You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we would like a way to distinguish dbname as a special parameter, one that we suggest the user provide at package binding time, rather than invocation time.
for example, the read-document action throws an exception if dbname is not provided, and it is unlikely that in normal scenarios dbname will be provided as input from a prior action in a sequence, or by a trigger as part of a rule.
whereas the docID field is much more likely to be in-flow data. therefore, dbname should be prompted for at package binding time
Solution: every cloudant action that specifies dbname as required should also specify it as bindTime: true
@starpit commented on Wed Jun 08 2016
we would like a way to distinguish
dbname
as a special parameter, one that we suggest the user provide at package binding time, rather than invocation time.for example, the
read-document
action throws an exception ifdbname
is not provided, and it is unlikely that in normal scenariosdbname
will be provided as input from a prior action in a sequence, or by a trigger as part of a rule.whereas the
docID
field is much more likely to be in-flow data. therefore,dbname
should be prompted for at package binding timeSolution: every cloudant action that specifies
dbname
as required should also specify it as bindTime: true@starpit commented on Wed Jun 08 2016
All of the cloudant actions that specify dbName as required must also specify bindTime: true
@markusthoemmes commented on Fri Mar 10 2017
@csantanapr move to catalog?
The text was updated successfully, but these errors were encountered: