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.

Sign up for GitHub

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

Jump to bottom

Add custom endpoint environment variables to all services. #924

Closed
11 tasks
quartzmo opened this issue Sep 26, 2016 · 4 comments
Closed
11 tasks

Add custom endpoint environment variables to all services. #924

quartzmo opened this issue Sep 26, 2016 · 4 comments
Assignees
@quartzmo
Labels
api: core priority: p2 Moderately-important priority. Fix may not be included in next release. status: will not fix Invalid (untrue/unsound/erroneous), inconsistent with product, not on roadmap. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@quartzmo
Copy link
Member

quartzmo commented Sep 26, 2016 •
edited
Loading

We already have emulator environment variables for setting the service location in Datastore and Pub/Sub. We should add similar variables for all other services (if possible.)

  • BigQuery
  • Datastore
  • DNS
  • Language
  • Logging
  • Pub/Sub
  • Resource Manager
  • Speech
  • Storage
  • Translate
  • Vision
@quartzmo
Copy link
Member Author

quartzmo commented Sep 26, 2016 •
edited
Loading

The existing emulator variable names are DATASTORE_EMULATOR_HOST and PUBSUB_EMULATOR_HOST.

@quartzmo
Copy link
Member Author

This is similar to googleapis/google-cloud-node#1630. Using the same environment variable names would be best.

@quartzmo
Copy link
Member Author

I believe this issue should follow the lead of GoogleCloudPlatform/gcloud-common#193. Changing title to reflect this new direction.

@quartzmo quartzmo changed the title Add emulator support to all services. Add custom endpoint environment variables to all services. Sep 30, 2016
@landrito landrito added priority: p2 Moderately-important priority. Fix may not be included in next release. status: acknowledged status: will not fix Invalid (untrue/unsound/erroneous), inconsistent with product, not on roadmap. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed status: acknowledged labels Mar 1, 2017
@quartzmo
Copy link
Member Author

quartzmo commented Mar 1, 2017

Closing this for lack of interest.

@quartzmo quartzmo closed this as completed Mar 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@quartzmo quartzmo

Labels
api: core priority: p2 Moderately-important priority. Fix may not be included in next release. status: will not fix Invalid (untrue/unsound/erroneous), inconsistent with product, not on roadmap. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@quartzmo @landrito