After diving into gcs permissions/acl/permission types + 
experimenting/inspecting, I've found out that zencoder indeed changed their 
default permission, probably from something project-private-ish to a more 
strict permission

Anyway I've also discovered that they allow you to send headers, so 
utilized it for "x-goog-acl":"project-private"
Solved the issues, result: wasted energy/motivation

I still think appengine should further integrate into gcs and make sure it 
has access to all files, I shouldn't have dived into the complicated 
dynamics of gcs
All these gcs issues that people are complaining about are caused by 
complicated permission dynamics, imo

On Saturday, September 28, 2013 5:44:04 AM UTC+3, Kaan Soral wrote:
>
> My brain is about to blow from gcs issues, just deleted a bucket because 
> it included "_" in the name (zencoder apparently has a bug in their gcs 
> integration that messes with the "_")
>
> After thinking everything was ok now, I've came across a new issue: 
> permissions
>
> I've compared the permissions that appengine generated files have and the 
> file zencoder put to my gcs bucket, and 2 group owner's are missing
> I've added one missing ID manually and things started working
>
> If the permission is missing, you get a 500 error while trying to serve 
> the file with self.send_blob(blob_key) -- and as all gcs 500 errors, it's 
> invisible from appengine logs
>
> Regardless of what happens (you might say that zencoder is the cause of 
> the issues, don't think so), I think the system should ensure that each 
> file in a google appengine app's bucket's should have the appengine's 
> permission (group or whatever) no matter what
>
> Would be great if this problem was solved quickly, however as it's 
> weekend, I don't have much hope, yet it's really blocking me on a personal 
> level
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to