Closed josephaw1022 closed 10 months ago
This might make more sense as a discussion because most of the items aren’t things that can just be added and require lots of new design. Much of this is out of scope for v1.
moved over to discussion
Link to discussion: https://github.com/dotnet/aspire/discussions/1570
I didn't feel like writing out a bunch of individual issues for each and every component, so I am just going to list some ideas out for some components that I think would be nice to haves for Aspire and am looking for feedback on potential ideas, push back on certain ones, which ones seem the easiest or realistic, or whatever is on your mind. Anyway here's what I've came up with.
Database
Storage
Secrets / Config
Messaging
Feature Flags
Emails
Data Aggregating
Api Gateways
Feature Flags
Emails
Search
Container Registries
CI/CD
Devtools
CLIs
Note
Some of these I think I would are more suited to be more additions / iterations to what's in place like search and emails.
Some of these I items aren't necessarily tied to a typical 'developer' workflow, but things that I do or have done locally and that I think would be nice to haves like cloud cli and or rancher. Just so that a non dev could easily spin up some dev ops containers and resources and see the relationship between the resources, the same way aspire is doing for .web, api, db, cache, and queue applications right now.