When new_id != old_id, uptest prints logs in a tight loop with no waits #168
Description
What happened?
If you're using uptest for a resource that fails the new_id == old_id requirement in the import test, uptest writes the output of kubectl get managed -o yaml to the console continuously in a tight loop, with no waits in between, generating unnecessarily large log files.
How can we reproduce it?
Currently I'm seeing this by running uptest on provider-aws/examples/s3/object.yaml
What environment did it happen in?
- Uptest Version: v0.6.1