tleyden opened a new issue #109: Specify doc id as parameter outside of doc body when creating doc via write action URL: https://github.com/apache/incubator-openwhisk-package-cloudant/issues/109 I'm trying to build a sequence of actions where one action produces: ``` { "doc": { "IsTruncated": false, "Marker": null, "Users": [ { "Arn": "arn:aws:iam::9798798:user/[email protected]", "CreateDate": "2016-01-11T23:49:40Z", "PasswordLastUsed": "2017-06-07T17:41:08Z", "Path": "/", "UserId": "ERXEAIDAHGJJK87878KKW", "UserName": "[email protected]" }, ... ] } ``` and the output is connected to a cloudant `write` action. Everything works, however it creates a new unique doc id every time the action sequence is invoked, which isn't what I want in this case. The only way that I can tell to have it write to the same doc id is to modify the upstream action to produce: ``` { "doc": { "_id": "aws_user_list", "IsTruncated": false, "Marker": null, "Users": [ { "Arn": "arn:aws:iam::9798798:user/[email protected]", "CreateDate": "2016-01-11T23:49:40Z", "PasswordLastUsed": "2017-06-07T17:41:08Z", "Path": "/", "UserId": "ERXEAIDAHGJJK87878KKW", "UserName": "[email protected]" }, ... ] } ``` It would be a "nice-to-have" option to be able to bind the doc id parameter to a cloudantdb write action so that when I call the action it will use that doc id, rather than having to include the `_id` parameter in the doc contents. Actually I just realized this is assuming it's even possible to create an action based on an existing cloudant write action and bind extra parameters to it. I'm not sure how to do that, but I thought I remember reading that it was possible. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
