Aditya Dani

@mcharris You can always send a pull-request with your changes and we will review it. Currently the travis build is passing for [master branch](https://travis-ci.org/libopenstorage/openstorage). We do have one flaky test...

@sp98 Yes feel free to send out a PR and we will review it. cc @dahuang-purestorage

@bnevis-i Thanks for reporting this issue. The `getVaultParam()` function is a misnomer since it always returns a string and could possibly be renamed to `getVaultParamString()`. For the `api.EnvVaultInsecure` parameter, I...

@sp98 Apologies for the delay. I have reviewed your PR and put some comments on it.

The portworx/sched-ops repo is still referring to this incorrect version of `kubernetes-incubator/external-storage`. This version dependency needs to be fixed in sched-ops.

Thanks for reporting this issue. We have already started the effort for supporting STORK on k8s 1.22. PR: https://github.com/libopenstorage/stork/pull/881

@lukegriffith This looks like a reporting bug from stork. We are planning to take this fix in the next release of stork. Thank you for reporting.

Thanks @lukegriffith for reporting this. We will add support for metrics for SnapshotSchedules in an upcoming release of stork.

Thanks for reporting the issue. We will look into it. Can you share which image scan tool you used to find these vulnerabilities?