You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have a step to check pod log contents in automated and convenient way.
Solution Description
It would be great if podLogs could be used in try blocks, and checked for contents (just as command/script).
Alternatives
Workaround is to wait for workload to complete and check pod logs:
- description: Check if pod logs contain information that the file was created.
script:
env:
- name: namespace
value: ($namespace)
content:
kubectl logs -n $namespace -l app=test-ebs-velero
check:
(contains($stdout, 'File /data/test.txt not exists. Creating')): true
Additional Context
No response
Slack discussion
No response
Research
I have searched other issues in this repository and mine is not recorded.
The text was updated successfully, but these errors were encountered:
Problem Statement
I would like to have a step to check pod log contents in automated and convenient way.
Solution Description
It would be great if podLogs could be used in
try
blocks, and checked for contents (just as command/script).Alternatives
Workaround is to wait for workload to complete and check pod logs:
Additional Context
No response
Slack discussion
No response
Research
The text was updated successfully, but these errors were encountered: