Tests assume some environment variables to be present about rust-s3

[jplatte]

Actually, this seems even worse. Do these have to be valid credentials for the tests to pass?

[durch]

@jplatte yeah, I did not have the bandwidth to mock the tests. Github actions associated with the repo pull in those secrets, if I recall correctly they get pulled into forked repo actions as well.

[durch]

Actually judging by the output of that PR they don't, now that is extra crappy, I'll pull your branch over to test

[durch]

@jplatte thank you for raising this, sorry for the crappy PR experiance, I'll have to figure something out here. I've merged your bumps, its published to crates.io as 0.24.0, I'll keep this issue open.

[jplatte]

If they were available to PR branches, they could be leaked through PRs that update the actions workflow.

Maybe you could add a realworld-tests cargo feature and add #[cfg(not(feature = "realworld-tests"), ignore] to these tests (+ update your CI config to pass --features realworld-tests).