AWS has been scanning the github repos for the exposed keys, We can probably use travis encrypt and read an environment variable instead.
On 2021/03/28 05:21:11, Clint Wylie <c...@apache.org> wrote: > Hi all,> > > I've noticed that the integration tests in Travis that use the segments> > stored in the static.druid.io s3 bucket are all failing, starting sometime> > between yesterday and today. Looking closer, they are failing to load on> > historicals with a 403 Forbidden error.> > > Is anyone familiar with the details on this bucket? The access key is> > https://github.com/apache/druid/blob/master/integration-tests/docker/druid.sh#L93,> > perhaps it has been disabled?> > > I have a copy of the segments from these tests, so I guess we could find an> > alternative way to load them and run the tests, if necessary, since this I> > think is going to be blocking CI until we get it fixed.> > > It was nice to have them in s3 since it was providing some basic tests on> > s3 deep storage, but I guess we could do these tests in an alternative way> > as well, and make the s3 integration tests be like the other cloud service> > tests and only run manually when bringing your own resources and> > credentials.> > -- Regards, *Himadri Singh* DevOps
