TaskQueueConfig.localTaskQueueConfig() is not prepared for handling migrated YAML files [138528920]

Fixed

Bug

Status Update

No update yet.

Description

zm...@skawa.hu

created issue #1

Jul 29, 2019 03:17PM

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered:
Trying to use the task queue configurations I migrated from XMLs to YAMLs based on the guide at

https://cloud.google.com/appengine/docs/standard/java/sdk-gcloud-migration#migrate_config_script in JUnit tests.

What you expected to happen:
I expected that in version 1.9.76 of the appengine-testing library (Java), the local Task Queue's builders are prepared to handle the YAML files created by the migration process, given that the previous, XML-based configuration is being phased out. However, this does not seem to be the case, as the line
TaskQueueConfig.localTaskQueueConfig().setQueueXmlPath("src/main/webapp/WEB-INF/queue.xml") throws a FileNotFound (quite expected, to be honest, since the file IS missing), while the line TaskQueueConfig.localTaskQueueConfig().setQueueXmlPath("src/main/webapp/WEB-INF/queue.yaml") throws a SAXException (also somewhat expected, since it's ... well, not XML).

Steps to reproduce:
Any unit test not using the default task queue should be sufficient, as the queue config file will be missing post-migration.

Other information (workarounds you have tried, documentation consulted, etc):
The migration guide does not detail specific use cases, and the TaskQueueConfig class in the SDK does not seem to contain corresponding functions for setting queue configs from YAML.

Comments

an...@google.com <an...@google.com> #2Jul 30, 2019 09:12AM

Assigned to gc...@google.com.

Hello,

Thank you for reporting this issue. I have forwarded the details to the App Engine engineering team, and it's currently being investigated.

Further communications will be made in this thread, however I cannot promise an ETA for the resolution of this issue.

Thank you for your understanding.

lu...@google.com <lu...@google.com> Oct 10, 2019 02:21AM

Reassigned to lu...@google.com.

zm...@skawa.hu <zm...@skawa.hu> #3Jan 7, 2020 10:26AM

Hi,

Has there been any progress on this?

lu...@google.com <lu...@google.com> #4Mar 24, 2020 05:17PM

Accepted by lu...@google.com.

Adding to current sprint.

lu...@google.com <lu...@google.com> #5Apr 15, 2020 06:05PM

Marked as fixed.

Fix is applied. Will need to find its way to a new SDK. A new API on LocalTaskQueueTestConfig has been added to define the yaml custom path. /**

Overrides the location of queue.yaml. Must be a full path, e.g.
/usr/local/dev/myapp/test/queue.yaml
<p>Once set, this value is persistent across tests. If this value needs to be set for an
operation specific to any one test, it should appropriately configured in the setup stage for
all tests.
@return {@code this} (for chaining) */ public LocalTaskQueueTestConfig setQueueYamlPath(String queueYamlPath);

Issue 138528920