Assigned
Status Update
No update yet.
Comments
da...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
ja...@gluky.com
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
da...@google.com
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
Description
But there is not a documented way of enabling those options when using ESP on App Engine Flexible. All that is explained in
endpoints_api_service:
name: ENDPOINTS-SERVICE-NAME
rollout_strategy: managed
That and 'config_id' for rollout strategy fixed is all that's documented. Are there any other options for enabling CORS in AEF?
It would be nice to be able to enable CORS (or any other startup option) by adding more options in app.yaml's endpoints_api_service:
endpoints_api_service:
name: ENDPOINTS-SERVICE-NAME
rollout_strategy: managed
cors_preset: basic
cors_allow_methods: ...
cors_allow_origin: ...