Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template validation errors when running ecs-colorapp.sh #136

Closed
qrobinson-starz opened this issue Apr 19, 2019 · 3 comments
Closed

Template validation errors when running ecs-colorapp.sh #136

qrobinson-starz opened this issue Apr 19, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@qrobinson-starz
Copy link

Describe the bug
When trying to run the ecs-colorapp.sh script, I get the following errors:
Unknown parameter in input: "proxyConfiguration", must be one of: family, taskRoleArn, executionRoleArn, networkMode, containerDefinitions, volumes, placementConstraints, requiresCompatibilities, cpu, memory, tags, pidMode, ipcMode

Unknown parameter in containerDefinitions[0]: "dependsOn", must be one of: name, image, repositoryCredentials, cpu, memory, memoryReservation, links, portMappings, essential, entryPoint, command, environment, mountPoints, volumesFrom, linuxParameters, secrets, hostname, user, workingDirectory, disableNetworking, privileged, readonlyRootFilesystem, dnsServers, dnsSearchDomains, extraHosts, dockerSecurityOptions, interactive, pseudoTerminal, dockerLabels, ulimits, logConfiguration, healthCheck, systemControls

Is there a way to work around this?
Thanks

Platform
MacOS
awscli-1.16.143
botocore-1.12.133

To Reproduce
Steps to reproduce the behavior:

  1. define required environment variables
  2. follow instructions up to running ecs-colorapp.sh

Expected behavior
The colorapp service should be deployed.

Config files, and API responses
Template validation error

Additional context
Add any other context about the problem here.

@qrobinson-starz qrobinson-starz added the bug Something isn't working label Apr 19, 2019
@lavignes
Copy link
Contributor

My first guess is that your ECS models are out of date.

It looks like you are using a cli version from yesterday https://pypi.org/project/awscli/1.16.143/

Can you double-check that you don't have an outdated model for ECS in ~/.aws/models/ that you may have added with https://docs.aws.amazon.com/cli/latest/reference/configure/add-model.html

@bigdefect
Copy link
Contributor

Hey there. I just went through the steps to verify and I was able to provision the tasks with a CLI on 1.16.140, the latest version currently available on homebrew.

That error message is the client-side validation in the CLI, which suggests the model in the version that's being invoked during the calls to ECS is out of date. proxyConfiguration was added to the ECS API a while ago, but I see you've listed a very new version of the CLI.

Could you confirm that you don't have multiple versions of the CLI installed, or maybe have overridden a model? It's possible that you have a separate one installed (for example through homebrew), and that's the one that's being invoked by default in the scripts.

@qrobinson-starz
Copy link
Author

Thanks for the response guys. I ended up uninstalling the cli and pulling it down from homebrew based on @efe-selcuk's suggestion and it seems to be working fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants