James E. Blair abad438e53 Align enqueue/dequeue events with trigger events ... EnqueueEvents and DequeueEvents are duck-typed as TriggerEvents when they are passed to source.getChange. TriggerEvents are always created in the context of a connection, so they have a hostname field and a name field, and name should never have the hostname. However, our current EnqueueEvents are created directly from client-side user input and accept any form of project name. This means when we get a change from them, we may end up with a Project that has a canonical name for it's "name" field. This could not only cause the enqueue event to be rejected, it could leak project objects. To correct this, perform some pre-processing on the input data to get separate host/name data for the project, and then use that to construct an Enqueue/DequeueEvent with the same field usage as a TriggerEvent. Change-Id: Ib596c282eba3a01c10d28593545e5d238d09de0c		2021-03-27 09:55:26 -07:00
..
git	Align enqueue/dequeue events with trigger events	2021-03-27 09:55:26 -07:00
main.yaml	scheduler: fix enqueue event to use canonical project name	2018-07-13 06:58:36 +00:00