-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(kvstoreentry/create): rework --dir #1371
Conversation
Ouch... the existing behavior was definitely broken. Thanks for fixing it! Thankfully the other 'entry' commands (config store, secret store) don't offer the Would you be willing to tackle improving the tests for this command to ensure that the behavior is correct? A proper test would have caught this originally, it would be great to have a way to avoid regressions. |
Sure, I will have a look. |
Done. Not sure why the tests are failing. I need to have another look, but at first glance these looked unrelated. |
FWIW the full test suite (running from this branch) passes for me locally. So yeah, the fact CI is failing is weird. |
I opened #1372 to test (it changes whitespace in a single file) and I'm getting the same errors so it looks like something is up with the CI / tests. |
I've never seen that test failure before, and the only recent change I can think of is that |
Same failure with Ubuntu 22.04. This will require some investigation next week. |
Test suite in 'main' passes locally using Go 1.23.4 and Rust 1.83.0. Very strange. |
Simplify code and exclude directory when inserting keys into the KV store. Before this change `create --dir=foo`, will create: foo/abc foo/def After this change: abc def
e16105d
to
6a76e65
Compare
I've updated this branch and the tests are passing now. PTAL. |
Simplify code and exclude directory when inserting keys into the KV store.
Before this change
create --dir=foo
, will create:After this change: