Hi Rodric,
I agree, that the key should not be passed to the action, if it is not
required.
But in my opinion, existing actions should continue to work without any
update. But I'm OK, if all newly created actions have the default, that
they don't have an API-key.
Greetings
Christian
Am Mi., 13.
2019-02-13 07:00:07 UTC - chetanm: Seeing following error in logs upon startup
```[2019-02-13T12:22:14.970Z] [ERROR] null
java.lang.NullPointerException: null
at
2019-02-13 17:14:23 UTC - Andrei Palade: @Andrei Palade has joined the channel
Thanks for the quick initial feedback.
I've opened a PR that excludes just the API key.
https://github.com/apache/incubator-openwhisk/pull/4284
This will be a breaking change - actions that are deployed already and
which need the key will need to be updated.
I added the annotation `-a
I agree the api_key is bad, when not using e.g. OW npm within the action. +1
for using an annotation to enable this.
activation_id is required to do the right thing for logging with concurrency
enabled - but I'm also not sure what risk it is to include that? It will be in
the response header
Hi,
I'm looking for feedback on the following issue:
https://github.com/apache/incubator-openwhisk/issues/4226
Actions receives the API key in the environment even if it is not
necessary. This should not be the default behavior. With the issue I'm
proposing that we flip the default and provide
I vote +1
[x] Download links are valid.
[x] Checksums and PGP signatures are valid.
[x] DISCLAIMER is included.
[x] Source code artifacts have correct names matching the current release.
[x] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[x] All files have license headers if
