Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for GAE Flexible #10344

Closed
1 task done
SudharakaP opened this issue Sep 3, 2019 · 4 comments
Closed
1 task done

Support for GAE Flexible #10344

SudharakaP opened this issue Sep 3, 2019 · 4 comments

Comments

@SudharakaP
Copy link
Member

SudharakaP commented Sep 3, 2019

Overview of the feature request

Currently we support GAE Standard and my belief is it's getting fairly stable after we fix #10336.

I would like to discuss about supporting GAE Flexible. The problem is Flexible environment by default only runs on Java 8. Although what I would like to try is to define a custom run-time to support Java 11. This way we could make our GAE generators consistent; both supporting Java 11.

Do you guys think this is a worthwhile effort? I am not sure how much demand we get for our GAE generator or if it's widely used by our users. Anyhow feel free to let me know your thoughts on this. 😄

If this is useful; I can work on this one next 😄

Motivation for or Use Case

Make the GAE generator support all App Engine environments so that users have a wider choice.

Related issues or PR

#10196

  • Checking this box is mandatory (this is just to show you read everything)
@saturnism
Copy link
Member

i don't personally feel this is necessary at this time. App Engine Standard Java 11 can do just about everything now. I would prioritize microservices first :)

@SudharakaP
Copy link
Member Author

@saturnism : Agreed. 😄 I wonder whether we should do this at all since doing too many things might make the generators unmanageable. We should probably focus on one stable monolith deployment method (i.e: GAE Standard Environment which we already have) and one stable micro-service deployment (which is underway). How about we close this issue ?

@saturnism
Copy link
Member

Agreed :) Let's focus on the 2 most important use cases first. Thanks for the help!

@SudharakaP
Copy link
Member Author

@saturnism : You are welcome 😄

@pascalgrimaud pascalgrimaud added this to the 6.4.1 milestone Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants