Represent Organizer in the DB

[ryanrightmer]

Organizers need to be tied to a property

Needs to hold basic contact information
Represent ID as a string ( we will hold their firebase auth id here eventually )

[JamesBock]

I think the most straight forward way we can do this is with Cloud Functions. Firebase Auth triggers

Firebase accounts will trigger user creation events for Cloud Functions when:

• A user creates an email account and password.
• A user signs in for the first time using a federated identity provider.
• The developer creates an account using the Firebase Admin SDK.
• A user signs in to a new anonymous auth session for the first time.

When a user is created with Firebase Auth, the Cloud Function will be triggered to send a PUT to the db to create a Organizer entity.

The Cloud Function is passed a UserRecord that has the uid of the created User, so we can use that to identify the db entity and assign Properties to it.

In the future, I hope we can selectively create db entries based on the Claims of the User, so when a User is created with whatever Claims a Organizer has, an Organizer is created in the db. Athough, this calls into question when and how the Claims are assigned. I think the only Users at this time are the Organizers so I don't think is a pressing issue for the MVP.