Support for ecsConfig for AWS Batch Forge #546
Description
Description
It looks like the ecsConfig option is not yet exposed
through the Tower CLI when creating AWS Batch Forge compute environments.
When attempting to pass --ecsConfig during compute environment creation, the CLI reports it as an unknown option.
Steps to Reproduce
$ seqerakit compute-envs.yml
INFO:root: Running command: tw -o json compute-envs list -w $ORGNAME/$WORKSPACE
INFO:root: Checking if name aws-non-wave-fusion exists in Seqera Platform...
INFO:root: Running command: tw compute-envs add aws-batch forge \
--name aws-wave-fusion \
--workspace $ORGNAME/$WORKSPACE \
--credentials my_aws_credentials \
--region us-west-2 \
--work-dir s3://sample/us-west-2/ \
--provisioning-model SPOT \
--max-cpus 500 \
--ecsConfig ECS_TASK_METADATA_RPS_LIMIT=120,180 \
--wait AVAILABLE
INFO:root: Command output: Unknown options: '--ecsConfig', 'ECS_TASK_METADATA_RPS_LIMIT=120,180'
Expected Behavior
The CLI should accept the --ecsConfig flag and forward its values to the AWS Batch Forge configuration, allowing users to define ECS task metadata and related settings.