1140138 - Define/document reserved values for identifiers (for testing/examples)

Status: RESOLVED FIXED

(Taskcluster :: Services, defect)

Description

[James Lal [:lightsofapollo]]

Similar to how example.com is defined as a domain that cannot be claimed we should define some "safe" values which are reserved for our identifiers.

workerType: example
workerId: example
workerGroup: example
provisionerId: example

--

These values are valid but should not be used (and may be enforced at a UI level/etc..)

Comment 1

[Jonas Finnemann Jensen (:jonasfj)]

I think this ties in to locking down scopes.
Especially if we extend tooling for auth to support exclusive scopes.

Maybe we can then make a set of perma creds specifically for testing.
It would probably have to be something like:
  test-provisioner-*

So that tests can set the last 5 characters to whatever, like "test-privisioner-24245",
just to reduce likelihood of collisions between tests.
Note: Randomly generating these is bad as tc-queue will create underlying azure queues
      that'll never be deleted (or we should implement a garbage collector for that).
      File a bug if someone thinks we need a GC, it should be reasonably simple to do.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

Yeah, I think this falls under the namespaces and is controlled by scopes..