CODEWITHSUNDEEP
google-app-enginegoogle-cloud-platform
R0w13y
R0w13y

Reputation: 13

How to view / download the current queue.yaml from GCP?

I am attempting to setup a local development version of an existing AppEngine application, I have everything running via dev_appserver and I can access the application, however none of the Task Queues are listed in the local admin interface only 'default' shows. I had hoped to download the queue.yaml and start it with dev_appserver as I did with the services but I cannot find the file anywhere in GCP to download.

I've searched the file system for queue: to no avail, I've searched through the gcloud cli docs and commands, doesn't seem to be any options to download or view only deploy the queue.yaml. There are no options in the GCP UI that I can see.

The queue is called with:

(new PushTask('/someUrl', [{params omitted}], ['name' => $taskName]))->add($abc);

The application throws the following error because it can't find the queues:

WARNING: exception 'google\appengine\api\taskqueue\TaskQueueException' with message 'Unknown queue'

How do I view or Download the Queue.yaml from AppEngine?

Upvotes: 1

Views: 293

Answers (1)

Dan Cornilescu
Dan Cornilescu

Reputation: 39824

AFAIK there is no place in GAE where you can specifically download the deployed queue.yaml, which is an app-level config file, shared by all services.

You can see some, but not all of the equivalent queue configurations parameters in Cloud Tasks in the Console developer (where the older Task queues now redirects). What's notably missing: the retry parameters and the target service (if any). Still, some info you could start with when re-building the queue.yaml file.

If you're lucky and symlinked the file into one of your standard environment services to keep the development server happy (see Google App Engine queue.yaml not working in development server) you may find the entire file content copied into the respective service deployment using the method described in: Google Cloud DataStore automatic indexing

The typical cause of vanished queues is missing the point that the queue config is shared by all services and deploying a new version of it with just one service in mind. The file content should actually be a combination of all queue configs needed by all services.

Upvotes: 1

Related Questions