Terry Howe
Terry Howe
Maybe if @gjenkins8 can get a chance to look at this
> So you mean the test is flaky? I had the impression that this test was written for the happy path and that there are other tests for the failed...
Revive this with fixing the conflicts?
It probably would not be difficult to add more logging in `pkg/kube`.
As I recall, if you want to override one value, it should look something like ``` volumes[0]: name: a persistentVolumeClaim: claimName: MY NEW CLASS ```
Do you think the change is complicated? I haven't worked that part of the code base to know history.
Seems reasonable to enable that. Do you want to raise a pull request?
Should we consider making the user specify the regular expression like the ls command? `bar.example.com*`
If this was to act like ls, users could in theory specify multiple regular expressions. `oras repo ls --oci-layout-path oci-dir/ *v1.31* *v.1.32*`
It seems like it would be easy to add a e2e test for this.