Remove compose default prefix (backward incompatible)

[yinshiua]

ecs-cli compose up and ecs-cli compose service up appends a prefix (ecscompose- and ecscompose-service-) to the task definition name and service name. There were many complains about the added prefixes previously (issues: #51, #82, #91, #97), so we made the prefixes configurable in the config file. I would like to remove the prefixes completely from the config file and not append the prefix at all. This will be a backward incompatible change, so we would like your opinion on this.

The prefix is currently stored in ~/.ecs/config.

[samuelkarp]

Would removing the prefix mean that ecs-cli could no longer manage existing clusters and services it launched when you upgrade it?

[yinshiua]

For clusters, we are using the default cfn default prefix, so if you did not customize the cfn prefix, you can continue to manage existing clusters.

For services, you can add the prefix to the project name (ex. ecs-cli compose --project-name "ecscompose-service-<project_dir>" service scale) to manage existing services

[samuelkarp]

I think the backwards incompatibility here is going to cause pain for people unexpectedly. If we're switching the default, there should be fallback logic to handle services that were created prior to this change.

[etsuo]

@yinshiua this is actually a bit of a bummer for us in that it now requires that we add yet another magic config file (~/.ecs/config) to get rid of the prefix. By itself, it's no biggie, but the less of these things we have, the easier it is for us to write scripts with no dependencies. Is there any way we could get an environmental variable to override the prefixes, or an argument?