[Mulit-Tenant] auth Tenant Admin Graphql API

[njlie]

Add the following to auth Admin GraphQL API:

type Mutation {
  createTenant(input: CreateTenantInput): CreateTenantMutationResponse!
  updateTenant(input: UpdateTenantInput): UpdateTenantMutationResponse!
  deleteTenant(input: DeleteTenantInput): DeleteTenantMutationResponse!
}

• createTenant mutation
• updateTenant mutation
• deleteTenant mutation
• document any new env vars and ensure helm charts are updated

Prerequisites

• [Multi-Tenant] auth tenant service #3122

[mkurapov]

What do we think about having this as an event we publish from backend to be consumed by auth and stored in the tenant TB?

Otherwise, we should find a way to hide this from the documentation

[njlie]

What do we think about having this as an event we publish from backend to be consumed by auth and stored in the tenant TB?

What kind of event did you have in mind? Pretty much any communication between these services will suffice.

[mkurapov]

I was thinking something like redis pub sub/streams as a message queue, but for V1 we can get away without using new patterns/technologies and just use a separate GraphQL API

[BlairCurrey]

Per our discussion on slack we decided to host this api on a new http server because:

1. we dont want to expose it on the graphql admin api
2. a new graphql api for this is a bit heavy-handed
3. a new http server would be a bit simpler than something like GRPC. No extra dependencies, codegen, etc.