Update exists annotation test to be more real world oriented #400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current example used for testing
exists
annotation consists of aNamespace
and aConfigMap
where theConfigMap
is an external resource with theexists
annotation. In the app there is no resource that depends on theConfigMap
, hence the example doesn't depict the correct use case for the exists annotation.The example is technically correct but I felt like it can be improved a little bit. So instead of the
ConfigMap
, I used theNamespace
as an external resource, and since theConfigMap
is supposed to be created inside thatNamespace
, it actually needs it toexists
.