There really should be a dotnet ecs deploy-service configuration file section including all the options

[jakenuts]

Describe the issue

I can't find any examples that show a full configuration file for dotnet ecs deploy-service

Links

https://github.com/aws/aws-extensions-for-dotnet-cli?tab=readme-ov-file#amazon-elastic-container-service-amazonecstools

[ashishdhingra]

@jakenuts Good morning. Thanks for opening the issue. The best place to find about ECS configuration is CloudFormation docs; for example, AWS::ECS::Service. Instead of including it here in the tools documentation which might get stale since service change all the time, with new options added, it's better to refer it at one place.

We will take a backlog item to add an example in Readme.

Thanks,
Ashish

[jakenuts]

Correct me if I'm wrong but the config file format for this tool might include elements from the ECS cloudformation templates but it seems to use different naming and conventions to cover the whole service and infrastructure deployment. If the tool is unsupported (as each AWS deployment tool I've tried eventually becomes) I can understand pointing users at the newer or legacy long term solution docs - but otherwise it seems a bit careless.

Almost every open source developer tool I've found on Github comes with some reasonably comprehensive documentation of the configuration files or options they support, how is it that this one from a giant service only has a minimal CLI -help option to fall back on?

[ashishdhingra]

Correct me if I'm wrong but the config file format for this tool might include elements from the ECS cloudformation templates but it seems to use different naming and conventions to cover the whole service and infrastructure deployment. If the tool is unsupported (as each AWS deployment tool I've tried eventually becomes) I can understand pointing users at the newer or legacy long term solution docs - but otherwise it seems a bit careless.

Almost every open source developer tool I've found on Github comes with some reasonably comprehensive documentation of the configuration files or options they support, how is it that this one from a giant service only has a minimal CLI -help option to fall back on?

@jakenuts We have created backlog item for this, which should probably include other supported services (lambda and beanstalk), if applicable, in addition to ECS service.

[ashishdhingra]

Correct me if I'm wrong but the config file format for this tool might include elements from the ECS cloudformation templates but it seems to use different naming and conventions to cover the whole service and infrastructure deployment. If the tool is unsupported (as each AWS deployment tool I've tried eventually becomes) I can understand pointing users at the newer or legacy long term solution docs - but otherwise it seems a bit careless.
Almost every open source developer tool I've found on Github comes with some reasonably comprehensive documentation of the configuration files or options they support, how is it that this one from a giant service only has a minimal CLI -help option to fall back on?

@jakenuts We have created backlog item for this, which should probably include other supported services (lambda and beanstalk), if applicable, in addition to ECS service.

@jakenuts Just to reconfirm, you are looking for all options which could be found using -help be listed in appropriate section in Readme; is this correct?