google-nomulus/core
gbrodman 92b83a9d7a Include Cursor in the initial SQL population (#1323)
The test for this also required a bit of a fix in the Cursor scope
initialization. If you persist a Key<?> in some object in Datastore, it
persists just the standard data you'd expect, basically the parent, the
kind, and the object's ID/name. Then, when you load it back in from
Datastore it uses the app ID of whatever environment you're loading in
(the Key contains this info even though it isn't included in the
toString() of Key)

If you persist the websafe string format of a Key (which is what we do
for Cursors), it includes the app ID so when you load it, it contains
the old app ID not the new one (if the app ID has changed).

In the pipelines, we use the standard default environment which has a
different app ID from the test environment that's set up by the
DatastoreEntityExtension.

As a result, we should check in Cursor to see if the key is *any*
cross-tld-key, rather than the exact one that exists within this app
environment.
2021-09-19 09:23:02 -04:00
..
gradle/dependency-locks Implement a util class to manage push queues using Cloud Tasks API (#1290) 2021-08-24 21:13:54 -04:00
src Include Cursor in the initial SQL population (#1323) 2021-09-19 09:23:02 -04:00
build.gradle Implement a util class to manage push queues using Cloud Tasks API (#1290) 2021-08-24 21:13:54 -04:00
Dockerfile Build docker image of nomulus tool (#142) 2019-07-16 20:18:44 -04:00