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
Historically, this was left as an unsolved problem; the fear was that if CI was able to run live tests against the cloud, an unscrupulous contributor could submit a PR that would (mascarading as a test) spin up instances for (say) bitcoin mining. There was also the problem of secrets management. None of those problems are unsolvable, but setting the ENV manually and running the tests locally is the short-term solution.
Provided as context, not as a counter-argument to doing the work.
Actually hitting AWS might be difficult (or at least too heavy testing for a gem). If we never fix this; we should at least add some testing e.g. we have a loadable gem, or one that gets as far as failing due to missing config. Will file a separate issue for that; we'd want to keep this issue for "real AWS" testing.
They're all being skipped because they need ENV vars set to actually hit AWS. I don't know how realistic this is for our CI setup.
The text was updated successfully, but these errors were encountered: