Hi Team, For some of the work I am doing (CosmosDB integration [1], S3 AttachmentStore) the test need to be run against a remote cloud service and thus requires access to access keys.
For CosmosDB PR I tried to read them from environment variables [2] and have them configured in the Travis settings for the repo. However it appears that those environment variables are not exposed for PR runs (for good reason) and instead are only accessible to PR which originate from same origin repo [3]. Due to this the build failed [4] for PR but passed on the build from fork [5] So I see following options 1. Have a branch in incubator-openwhisk repo and then create a PR from that. 2. Keep working on a branch in fork and then reviewers can run the test on there setup by providing the credentials directly. So any thoughts on how to proceed on this work? I prefer #1 but that would require me to work on a branch in incubator-openwhisk repo and create PR from that Chetan Mehrotra [1] https://github.com/apache/incubator-openwhisk/pull/3562 [2] https://github.com/apache/incubator-openwhisk/pull/3562/files#diff-4193e72115f45d80db211b31c0eeffd8 [3] https://blog.travis-ci.com/2013-06-10-secure-env-in-pull-requests [4] https://scans.gradle.com/s/pg4t4okpmhrle/tests/ubbzynwftyf6i-6kwrh3kd4tzye [5] https://travis-ci.org/chetanmeh/incubator-openwhisk/branches (see status for artifact-store-cosmos)
