Docker Compose publishing

[prom3theu5]

Description

Starting to roll in the expansions to the publishers, to allow output in the various target asset types.
Ignore a lot of the processing within the Output generators for now, lots of changes to come - this is more for transparency / visibility atm.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[davidfowl]

One of the things we will want to do is also look at modeling docker compose files, helm and k8s as resources much like how we do with the azure resources. (Cdk like objects for each)

[prom3theu5]

One of the things we will want to do is also look at modeling docker compose files, helm and k8s as resources much like how we do with the azure resources. (Cdk like objects for each)

Thats probably a good call. It would - in turn, eventually allow compose and helm charts etc to be added to an AppHost as templates etc much like bicep supports.
We'd probably have to build a similar abstraction with properties wrapped in things like YamlValue, YamlDictionaryOfT etc

If we eventually went the AppHost route for addition / inclusion of those though, the provisioner would be pretty "full on" in terms of effort ^^

[davidfowl]

If we eventually went the AppHost route for addition / inclusion of those though, the provisioner would be pretty "full on" in terms of effort ^^

This is the plan 😄, but we should be incremental here so we can build up before we replicate the wrong pattern everywhere.

[davidfowl]

Thoughts on https://cdk8s.io/ @prom3theu5 ?

[prom3theu5]

Thoughts on https://cdk8s.io/ @prom3theu5 ?

I am a fan. Also, c# support was recently added.
Personally, i've always tended to use Pulumi's Automation API though for C# based deployments when i'm asked to bundle things a dev team can use directly for things like local-dev etc Example / Docs

I've also been following: Timoni quite closely

But thats what we're going to eventually be able to replace with Aspire 😄

Are you thinking about including cdk8s projects in the AppHost?

[davidfowl]

Are you thinking about including cdk8s projects in the AppHost?

Only if they had C# support and it was extensible (and not going to die 😄).

[davidfowl]

We could contribute to it as well.

[prom3theu5]

Are you thinking about including cdk8s projects in the AppHost?

Only if they had C# support and it was extensible (and not going to die 😄).

They do now - its not documented, but it was merged in 2 weeks ago ^^

[davidfowl]

These packages are in preview and we’ll keep it there until we get to a good approach. That said I’d like us to iterate on small commits, especially when we have something that we can try out.

what do you think is the next step here @prom3theu5? We should pick one end to end to flesh out the “problems” and interactions between the cli and publisher (including stare management and prompting etc)

[prom3theu5]

These packages are in preview and we’ll keep it there until we get to a good approach. That said I’d like us to iterate on small commits, especially when we have something that we can try out.

what do you think is the next step here @prom3theu5? We should pick one end to end to flesh out the “problems” and interactions between the cli and publisher (including stare management and prompting etc)

Yep!

Compose is the easiest to work through, once thats in place - its relatively quick to work through the rest, as long as the pattern is satisfactory
I've made a start firming that up - still a few issues i need to work through tomorrow night, but we are going to have to capture some input somehow if not all parameters and secrets have values set etc

[mitchdenny]

Thanks for all your efforts @prom3theu5

[prom3theu5]

Cheers Mitch 😃