Feature #14260
Updated by Tom Clegg over 5 years ago
When creating a container request, a client can specify an API token to be used in a container. When running a container on a cluster other than the requesting user's home cluster, this allows the container to read collections on other clusters. runtime_token: * is not provided in API responses (similar to secret_mounts) * can be retrieved by the dispatcher that has the lock lock, using the @/arvados/v1/containers/$uuid/auth@ a dedicated API (as usual) (similar to secret_mounts) * can be set to any string when creating a container request * is ignored when considering containers for reuse * is used instead of a random secret in Container#assign_auth