Git based workflows

[maxgurewitz]

This issue will describe the work that needs to go into implementing git based workflows, as described in Dittofeed's docs. This is a major initiative and will require several new internal features.

Resource Mapping

A way to map database resources to and from yaml configuration.

• A function for mapping resource values held in postgres to a YAML based dsl / config, resourcesToConfig.
• A function for diffing resource config files and updating resource values held in postgres, updateResourcesFromConfig.
• A new branch column on resource data models, updating their unique columns from @@unique([workspaceId, name]) to @@unique([workspaceId, name, branch]). This value would default to "main".

Authorization

An authorization scheme to protect resources on the main branch. When workspaces are "protected", you should not be able to update resources on the main branch directly.

• A function canUpdateResource which accounts for the branch of the resource that's being updated.
• Using this function in the API to prevent updates to protected resources.
• Incorporate this function into the dashboard, to prevent forbidden updates.
• A way to make a workspace protected in the settings.

Branching

• An API endpoint for creating new branches, and switching between them, to be integrated into the dashboard.
• An API endpoint for deleting branches, to be integrated into the dashboard.
• An API endpoint for rendering diffs between workspace branches.

Github App.

We will need a git app reading from, and writing to github. This app will be used to write config to git when changes are made, and read them back from main.

The previously discussed updateResourcesFromConfig will be called on the main branch when changes to the config are made.