Implement "read-only until authenticated" mode for meltano.meltanodata.com
Follow-up from https://gitlab.com/meltano/meltano/issues/1348
As confirmed by Danielle in https://gitlab.com/meltano/meltano/issues/1348#note_261211584, we intend for meltano.meltanodata.com
to be our own instance of Meltano, with our own data (preferably real, but probably dummy in the case of some taps), reports and dashboards, to show guest users the value that Meltano can deliver to a team once it's fully set up.
This means that any kind of write actions by guest users are problematic, and the simplest solution would be to have the instance be in read-only mode until authenticated, with signing in unlocking all the regular read-write permissions.
This would be a third option in between the two current extremes:
- regular instances, including
meltano.meltanodata.com
right now: fully open, read-write to the world - NEW for
meltano.meltanodata.com
: read-only to the world, read-write once authenticated - other
*.meltanodata.com
instances: closed to the world, read-write once authenticated