Using Aspire generated deployment manifest in production #10803
mehdihadeli
started this conversation in
General
Replies: 1 comment 1 reply
-
https://medium.com/@davidfowl/bridging-the-gap-the-future-of-aspire-6eb421a92ab8 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have this concern in my mind, Should we use generated manifests from Aspire publish like Kubernetes and Azure directly in production?
Suppose we have a dedicated DevOps and platform team, and they are responsible for setup all infrastructure related things with YAML, Terraform, Bicep, ... in the source control with handling all detail configurations and security related things.
Now what happens after switching to use aspire and its publishing mechanism? We should get publish output of our aspire and after that customize and maintain it in the source control for our DevOps team? Should we consider it as a complete replacement for our entire DevOps infrastructure and implement all customizations directly in the C# code, similar to how Pulumi operates?
Is aspire publish a replacement for infrastructure as code tools like Terraform?
Beta Was this translation helpful? Give feedback.
All reactions