dankor commented on PR #29573: URL: https://github.com/apache/superset/pull/29573#issuecomment-2226946246
> Hi, @dankor! Welcome to the Superset GitHub! > > Can you add some context on why these fields are needed? Thanks! Hi @betodealmeida! Sure! I'm working on establishing a robust and granular deployment process for Superset. The core issue here is similar to why we expose these UUIDs in the import/export API: we need persistent identifiers across multiple Superset instances. You might suggest extending the import/export API instead, but we’re encountering several challenges: - No support for tags, roles, etc. - Deprecated resources aren’t cleaned up. - Archives are much harder to debug compared to classic CRUD operations. What I’m really aiming for is a declarative way to manage Superset resources (let’s call it a "report-as-code" approach). Imagine having a development environment where everyone can experiment freely. Once a report is ready, it can be committed to git, reviewed, and then deployed to higher environments. Ideally, I envision mature version of [this](https://github.com/platacard/terraform-provider-superset), but supporting all types of resources. You can check out a proof-of-concept in this [video](https://www.youtube.com/watch?v=ZSG8XRPzgUo), though no code is available, just video. My plan is to implement this feature incrementally, starting with minor changes and aligning as closely as possible with upstream. Hope this makes sense! Let me know if you're open to these kinds of contributions and what concerns the community might have. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
