From 4486b69e8b23a8b6f667cf7a43b8ed776ef5ebf2 Mon Sep 17 00:00:00 2001 From: Jonathan Amsterdam Date: Thu, 27 Aug 2020 11:47:57 -0400 Subject: many: use OnGCP instead of OnAppEngine Where it makes sense, call the new Config.OnGCP function to determine if we're running anywhere in GCP (AppEngine or GKE). Change-Id: I1efee29b0c32f9d4818d1a7514b44ae65d7aa252 Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/251059 Reviewed-by: Julie Qiu Run-TryBot: Julie Qiu TryBot-Result: kokoro --- internal/queue/queue.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'internal/queue/queue.go') diff --git a/internal/queue/queue.go b/internal/queue/queue.go index 0b042819..2cde9847 100644 --- a/internal/queue/queue.go +++ b/internal/queue/queue.go @@ -32,7 +32,7 @@ type Queue interface { // New creates a new Queue with name queueName based on the configuration // in cfg. When running locally, Queue uses numWorkers concurrent workers. func New(ctx context.Context, cfg *config.Config, queueName string, numWorkers int, db *postgres.DB, processFunc inMemoryProcessFunc) (Queue, error) { - if !cfg.OnAppEngine() { + if !cfg.OnGCP() { experiments, err := db.GetExperiments(ctx) if err != nil { return nil, err -- cgit v1.3-5-g9baa