I am looking to set up a POC for Elementary OSS for my org, and before I go through the effort of a full production setup (service user, task runs, etc.), I would like to test the CLI locally. However, the elementary profile says it requires the ability to write to the elementary schemas. Why is this? Isn't the report generation just querying the elementary tables?

Hi Rebecca, Elementary also keeps state for things like the amount of failures etc. This way you are able to see data quality issues over time. Elementary needs to write this data to that schema. Hope it makes sense!

Isn't the user running dbt writing to their own elementary schema with those things? It doesn't need an elementary profile for that, correct? I'm curious about the command line tool's need for a profile that has write capabilities. In my preliminary explorations, it seems I am able to run the report just fine on production elementary schema where I don't have insert/update/create permissions. Is it just a subset of features like upload-source-freshness that need a user to be able to write to the schema? At any rate, I'm happy to be able to run the report as part of this POC evaluation for my team.