Moving to dev list. This looks like a bug in the build workflow but I cannot pinpoint it. In the GCS UI all objects have Public Access: Not Authorized property. This explains why you cannot download them. However workflow uses "gsutil cp -r -a public-read ..." to copy the object to GCS, and "-a public-read" is meant to make objects readable to all consumers. I am not sure why that is not working as expected.
Someone with more experience on GCS ACLs might be able to help. On Fri, May 21, 2021 at 5:37 AM Aris Tritas <a.tri...@gmail.com> wrote: > Hi, > > In the process of installing a nightly version of the python SDK, I am > denied access to the SDK artifact archive on the GCS staging bucket. > Individual files from the CI run are accessible (incl. wheels). > > The location to the GCS blob was taken from the latest CI run report at > > - > https://github.com/apache/beam/runs/2636176987?check_suite_focus=true#step:3:7 > resolving > to > - > https://storage.googleapis.com/beam-wheels-staging/master/40326dd0a2a1c9b5dcbbcd6486a43e3875a64a43-862470639/apache_beam-2.31.0.dev0.zip > > Am I doing something wrong or is there a reason the SDK archive is > inaccessible? > Best, > > -- > > Aris Tritas > > E-mail: a.tri...@gmail.com > Mobile: +33(0)6 66 95 04 02 <+33%206%2066%2095%2004%2002> > Linkedin: https://www.linkedin.com/in/aris-tritas/ >
