If nothing has changed on the second run then it's behaving correctly. I'm have a related problem (which lead me to this thread) where I do change the definition in the playbook but Ansible doesn't create a new revision. In my case I'm updating the tag in the image. In your example I'd be updating image: "http:2.4" to image: "http:2.5"
Has anyone else seen this issue before? On Thursday, June 30, 2016 at 9:38:14 AM UTC-7, Niko Ruotsalainen wrote: > > Hi, > > I'm trying to use ecs_taskdefinition module to create task definitions to > ECS. > > I'm using example from > https://docs.ansible.com/ansible/ecs_taskdefinition_module.html > > --- > > - hosts: localhost > tasks: > - name: "Create task definition" > ecs_taskdefinition: > containers: > - name: simple-app > cpu: 10 > essential: true > image: "httpd:2.4" > memory: 300 > mountPoints: > - containerPath: /usr/local/apache2/htdocs > sourceVolume: my-vol > portMappings: > - containerPort: 80 > hostPort: 80 > - name: busybox > command: > - "echo 'LOL'" > cpu: 10 > entryPoint: > - sh > - "-c" > essential: false > image: busybox > memory: 200 > volumesFrom: > - sourceContainer: simple-app > volumes: > - name: my-vol > family: test-cluster-taskdef > state: present > register: task_output > > - debug: var=task_output > > > And output is: > > $ ansible-playbook playbooks/create-ecs-taskdefinition.yml > > PLAY [localhost] > *************************************************************** > > TASK [setup] > ******************************************************************* > ok: [localhost] > > TASK [Create task definition] > ************************************************** > ok: [localhost] > > TASK [debug] > ******************************************************************* > ok: [localhost] => { > "task_output": { > "changed": false, > "taskdefinition": { > "containerDefinitions": [ > { > "cpu": 10, > "environment": [], > "essential": true, > "image": "httpd:2.4", > "memory": 300, > "mountPoints": [ > { > "containerPath": "/usr/local/apache2/htdocs", > "sourceVolume": "my-vol" > } > ], > "name": "simple-app", > "portMappings": [ > { > "containerPort": 80, > "hostPort": 80, > "protocol": "tcp" > } > ], > "volumesFrom": [] > }, > { > "command": [ > "echo 'LOL'" > ], > "cpu": 10, > "entryPoint": [ > "sh", > "-c" > ], > "environment": [], > "essential": false, > "image": "busybox", > "memory": 200, > "mountPoints": [], > "name": "busybox", > "portMappings": [], > "volumesFrom": [ > { > "sourceContainer": "simple-app" > } > ] > } > ], > "family": "test-cluster-taskdef", > "revision": 1, > "status": "ACTIVE", > "taskDefinitionArn": > "arn:aws:ecs:eu-west-1:123456789012:task-definition/test-cluster-taskdef:1", > "volumes": [ > { > "host": {}, > "name": "my-vol" > } > ] > } > } > } > > PLAY RECAP > ********************************************************************* > localhost : ok=3 changed=0 unreachable=0 failed=0 > > So far all good. But when I run script again, it does not create new > revision of task definition what I would expect to happen and output is > exactly the same. Am I missing something or is this some kind of bug? > > $ ansible --version > ansible 2.1.0.0 > > I also tried creating task definition with AWS CLI and it work as > expected. Second run create new revision of task definition. So thats why > I'm asking this question here. > > BR, > Niko > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/cba6ef86-417d-4f3c-9cc6-5f96035cab34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
