tl;dr; Has anyone made a end-user-focused Catalogue powered by Pulumi? Good morning Pulumiverse, I woke up with an idea for for a personal project and I don't have enough experience with Pulumi to know if its crazy or silly, or an exciting blend of the two. I'm thinking of kicking it off over the quiet holiday period and would appreciate any thoughts or feedback (for or against). I work for SquaredUp (we make flexible dashboards) I want to build a UI driven catalogue of all sorts of great templates so a users can pick and choose exactly what they want and have it built out. I'd also like users to be able to submit their built dashboards for others to consume and customize. While drafting out some ideas I realized this could just be making another proprietary template format, and thats when it struck me, if I can author a Native Provider for SquaredUp my catalogue could be powered by Pulumi and all the cool stuff that comes along with it.

writing a native go provider will only allow you to generate sdks for the other languages so yes, others would use those to as-code their squaredup dashboards but I don't see how, on to of that, you'd have a GUI that drives all that(?) it would have to generate pulumi code like maybe how https://www.pulumi.com/ai does(?)

it would have to generate pulumi code like maybe how https://www.pulumi.com/ai does(?)

Hello Paul, I think it would generate code similar to that (less AI, more transpiling probably). I'm envisioning a customer connecting their GitHub repo to this catalogue tool and building or modifying their environment in the UI, then on save it updates the Pulumi code in the repo and executes it. I suppose like a WYSIWYG editor, where you could then step lower and do non-UI supported items with a couple code tweaks. Possibly overly complex and not useful for the community