Open hassenius opened 3 years ago
I'm facing this problem too
thanks for the heads up... I will look into this in the next couple of days!
well... I obviously meant in the next couple of years :). This is old and expected to still be an issue. Working for inclusion for next month.
Background: I have a
00-assert.yaml
looking like this:kubectl kuttl test <path>
yields the desired result of setting a custom timeout for the state to be reached for the specific assertion (at least it appears like it is, and the test case completes successfully without timing out after the default 30 seconds)However, I would also like to use the same declared assets to "point" at an existing environment, so I would have expected to be able to just do
kubectl kuttl assert <path>/test-*/*-assert.yaml
What happened:
kubectl kuttl assert <path>/test-*/*-assert.yaml
yieldsif I remove
from
*-assert.yaml
files I get the expected result:or
What you expected to happen:
kubectl kuttl assert
to be able to handlekind: TestAssert
in the same waykubectl kuttl test
doesHow to reproduce it (as minimally and precisely as possible): Create a
00-assert.yaml
with aAnything else we need to know?:
Environment:
kubectl version
):kubectl kuttl version
):Darwin
uname -a
):19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64 x86_64
brew