Oh, so the new "cloud integration" projects are actually different then the 'old' API projects - I hadn't realize that.
I guess then, if I want the integration, I have no choice but to do as you suggest: recreate my API project as one of the new projects. Thanks for the info, Tom On Thursday, September 5, 2013 2:13:48 PM UTC-4, Jason Collins wrote: > > I don't think you can do what you're looking to do. > > Do you want them associated to get some of the nice, automatic service > account authorization bits? You can do same (I believe) by adding the GAE > service account to the Team tab of your existing API project. > > That said, it feels like more and more feature sets will be built around > the tight integration of an API project (really a "cloud" project) and your > GAE application, so it might be worth your while to migrate to the new > "cloud integration" projects. We did this, though it was somewhat painful. > Hopefully, I've interpreted the vision correctly! > > j > > On Thursday, 5 September 2013 11:03:30 UTC-6, Tom wrote: >> >> I decided to try out the new Cloud Console and associate my API project >> with my GAE/J project - both already existed. >> >> After fooling around a bit but not succeeding, I click on the 'cloud >> integration' option in my GAE application settings - not surprisingly this >> associated my GAE project with a brand new API project. I can delete that >> newly created project, but it just creates another and now things are >> starting to get weird so I better stop. >> >> Any suggestions? Thanks. >> >> >> -- 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.
