…pache#4294)

1. Fixed 2 typos that refer to non-existing response 'TooManyRequsts'
2. Updated description of PUT method for rule
3. Updated description of PUT method for trigger
4. Created new definition ActivationBrief
5. Changed response type for GET activations to refer to ActivationBrief instead of EntityBrief, which didn't match the actual response
6. Added attribute statusCode to definition ActivationBrief and Activation
7. Modified description of GET activations apache#2271
8. Added operationId to GET activation logs and result (apache#318)
9. Removed the init attribute from the ActionExec definition (apache#4201)
10. Use of 2 spaces for indentation, which is the default when working with the Swagger editor, instead of the four spaces used.

…e#4297)

* Improve container factory documentation

Explicitly list some of the expectations and requirements an actual container factory / container implementation needs to satisfy. Addresses apache#4002.

* Address review feedback

…Apache Hadoop clusters. (apache#4129)

Fixes apache#4269

…ryTests (apache#4305)

* Look up runtime tag for YARN tests

* Scala formatting

* Use custom manifest for YARN tests

* Remove imageTag method

)

…ily (apache#4299)

* wait for sentinel only in case no timeout occurred

* introduce timeout annotation

* nodejs:6 logging timeout action w/o busy loop

* do conversion from FiniteDuration to Duration

…pache#4275)

* Collect and log CosmosDB query metrics when extra logging is enabled Fixes apache#4268

If there is an deployment with several controllers, the test `Whisk rules should preserve rule status when a rule is updated` fails intermittently. The reason is, that there are several modifications on the rule. These modifications are already retried. But enabling and disabling the rule also modifies the database document. But that change is currently not retried.
This PR puts the enabling/disabling of the rule into the retry block as well to make this test more stable against our eventual consistency.

Co-authored-by: Somaya Jamil <[email protected]>

…202-b08. (apache#4318)

Records the clusterId (if configured) with the updated document while persisting in ComosDB. This is an optional property. By default no `clusterId` info is saved

* Update to CosmosDB SDK 2.4.2

* Remove logic related to storing attachments in CosmosDB

* Reduce throughput for test to 400

…ache#4284)

* Factor out some annotation names to WhiskAction singleton.

* Omit API key unless requested explicitly.

* Add an annotation provide-api-key which causes an API key to be passed to the action context.

* Modify Parameters.isTruthy to allow for caller to specify how it wants to treat a missing key.

Default is missing key -> false (preserving behavior).
Add test for isTruthy.

* Treat a missing provide-key-annotation as truthy annotation.

Actions that already exist without the annotation will receive the key as they might already expect.

* Add container proxy test.

* Update tests for new system annotation.

* Allow pre-existing actions to be exempt from new system annotations.

* Update docs.

* Kamon Gauge abstraction

* Switch to gauge metric

…ation (apache#4334)

… with new format. (apache#4346)

* Adapts test harness to parses activation ids from wsk activation list with new format.

…4348)

Ignores the json records which have some of the required fields missing and replaces them with the error message from the parsing

…pagation (apache#4340)

…e#4345)

Closes-Bug: apache#4335

This PR moves the config of the runtimes-registry to pureconfig. In addition it adds the ability to provide credentials for this registry. They are not used yet in the default implementations of the container factory. But they can be used in the SPIs.

…ression in performance tests. (apache#4353)

Reverting back to adoptopenjdk/openjdk8:x86_64-alpine-jdk8u172-b11 from adoptopenjdk/openjdk8:x86_64-alpine-jdk8u202-b08 (commit) as we see regression in Latency.

After briefly debugging, we found that the time was lost between Controller->Invoker & Invoker->Controller (as reverting version already helps to improve the problem there seems to be an issue with the communication with kafka). We didnt find a quick solution so reverting back to the old version, and in the meanwhile will continue to look for the root cause.

…ist (apache#4355)

A private docker registry has been set up for the VMs dedicated to
OpenWhisk deployment. This PR adds the feature to  push the controller
and invoker images into this private registry, so that they can be
accessed by all the VMs.

…#4360)

* Enable soft deletion of documents in CosmosDB

…4385)

Co-authored-by: steffenrost <[email protected]>

wskdeploy is now distributed as a subcommand of wsk (wsk project),
so no need to include a wskdeploy executable.

This PR will utilize three VMs as the edge machines, so that we can run 3
openwhisk depoyments at the same time instead of one.

…he#4396)

Due to Graphite convention metric names ending with `count` are aggregated with max which is not desirable in some cases. So change the name to use a neutral suffix

)

…apache#4387)

…che#4290)

* Skip clustering when nodes are already in the cluster
* Enable couchdb persist_path for a distributed environment as well

…4423)

Co-authored-by: Sugandha Agrawal <[email protected]>

* Enable attachment reads from CloudFront

* Updating Node.js and Docker docs.

Adding common use-case instructions based on community feedback.

* Fixing scancode issues

Great job on the updated docs but I think we should remove the `ibmcloud` part from the commands as we should remain vendor agnostic.

* actionloop docs

* license

* fixes

…che#4450)

Fixes apache#4265

If we are switching the default runtime to nodejs:10,
we should change the default stemcell configuration to match.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* Touch-up pass on ActionLoop docs.

* complete update of launcher xlate to ruby instructions

* complete update of launcher xlate to ruby instructions

Suggested workaround for Java related error that may appear on ubuntu 14.

…pi (apache#4295)

* correct inconsistent error handling in the couchdb rest store

* remove duplicate metrics by making exceptions distinguishable

…e#4211)

* Add origin path

* Update document

* Apply review

* Update annotations and add a type decorator

* Refactor code

* Fix testcase

* Reformat code

* Refactor code

* Remove unused code

…e#4475)

* Additional cleanup and simplifications for the ActionLoop docs

* Additional cleanup and simplifications for the ActionLoop docs

* Updating runtimes to include new Node.js v12 image.

- Updated runtimes manifest
- Added API documentation
- Minor updates to docs
- Added automated test case

* Fixing accidental default flag for v12

* Update docker version in the controller and guides
* Update travis configuration to install docker=18.06.3
* Separate docker installation from the travis setup script
* Add docker setup script
* Add CoordinatedShutdown to cleanup runtime containers
* add a configuration for root runc dir
* Disable runc use in Jenkins environment
* Add comments which explain the correlation among the version docker and runc and the type of user
* Reenable Docker remote API again

…ame (apache#4488)

Add `pip install docker` to Dockerfile for ow-utils to fix problem pulling docker images

* Switch to consistent indexing policy
* Remove reference to Range index
* Tweak indexing policy comparison to only check for included and excluded path
Do not check for Index type as now there is only one which is Range for our cases
* Use implicit logger
* Excluding root path should be using `/*` instead of `/`

Updates to Alpakka S3 Connector v1.0.1 release.

This commit also includes some fixes related to apache#4484 which were causing compatibility issues with existing setup. For existing setup indexes were still using `Hash` indexing and that caused failure while creating `IndexingPolicy` upon collection read. So added back support for `Hash` index but not using them to create new indexes now

Record collection usage stats for CosmosDB so as to enable tracking the growth of collection in  terms of storage size, document count and index size over the period of time. It also enables tracking any indexing progress if any change is done in Index configuration.

Note that Count stats are currently not exposed via Azure Portal

Further this commit also enables emitting verbose trace for query when in debug mode. This would simplify any query performance analysis.

Fixes apache#4489