Alexander VanTol

I think this could be generalized as a link similar to self_uri, except returning arbitrary JSON representing additional object file metadata for that DRS ID? Then there's arguably no need...

it's not really based on lilypond, there are some utilities that help to generate some basic lilypond strings (I'm using it for simple PDF creation at the moment). I was...

One of the main goals of DRS is to abstract the locations of files with a persistent identifier, such that a change in location or file name doesn't break existing...

I understand what you're saying but all the things I previously said still stand. Requiring an additional `name` is breaking the critical abstraction that DRS provides and potentially sets a...

How are these getting to env vars for Helm Charts? We put a lot of work into the YAML-based configuration support for default values and allowing overrides. It's not clear...

I think we should handle clients during syncing.. if we are specifying user policies in the `user.yaml` we should be able to specify client policies as well. It would be...

Hey @VJalili ! thanks for the input, we actually don't support email as a separate field, we bundle all the user info into the context field and provide that under...

we could additionally support the `email` field as the OIDC spec defines, but then the `email` field would end up outside the `context` block, per the spec. Furher conformance to...

I'd prefer you fix the Black formatting suggestions, but I'm approving so I don't forget to later :P

In general the comments above look good, thanks for all the detail. This part: > indexd returns a 403 Forbidden for all reads with id e.g. GET /index/ I think...