jetstack-secure
jetstack-secure copied to clipboard
jetstack
Open source components of Jetstack Secure
Can we remove redundant logs about the `server missing resource for datagatherer`? It makes it very difficult to actually see logs that do mean something. **What happened?** Take a look...
Ref: [VC-36593](https://venafi.atlassian.net/browse/VC-36593 "AGENT: Add unit test to make sure that --venafi-cloud can still be used with --client-id") While preparing for https://venafi.atlassian.net/browse/VC-36353, I found that I was using `go run ....
I kept having: ``` $ git rb -i master warning: refname 'master' is ambiguous. warning: refname 'master' is ambiguous. ``` I noticed that the `master` tag exists along side the...
I think most of the jetstack-agent stuff has been removed and is no longer relevant to what we do day-to-day. This is a first step towards cleaning up the code...
This seems like a simple enough way of uniquely identifying a cluster. Google searches show that this pattern is used elsewhere. It seems fair to assume that if the kube-system...
Move the `venafiConnection` option out of the `crds` sub-object. This matches the config structure we have in other projects. Next, in a future PR, we can add the `serviceAccountNamespace` option...
Ref: [VC-35565](https://venafi.atlassian.net/browse/VC-35565) [VC-35565]: https://venafi.atlassian.net/browse/VC-35565?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
The govulncheck action is broken https://github.com/jetstack/jetstack-secure/actions/workflows/govulncheck.yaml ``` [govulncheck: pkg/client/client_venconn.go#L14](https://github.com/jetstack/jetstack-secure/commit/2d13638d7f1a7d149d625ce1127fb95c4a5d1809#annotation_29287405002) github.com/jetstack/[email protected]: invalid version: git ls-remote -q origin in /home/runner/go/pkg/mod/cache/vcs/e1445deb79b4ca14ee954e0f79f4034748b368f02a81510920a656b6ce2c6380: exit status 128: ``` So until we fix that, we have to...
In #612, it is written: ```go // TestNoneCache demonstrates that the cache helpers do not crash if passed a // non-cachable object, but log an error with a reference to...