workflow-cd-ecspresso.yaml fails

[ronaldsteen]

I've been following the "setting up ecspresso" guide, and have reached starting to trigger the workflows: https://docs.cloudposse.com/layers/software-delivery/ecs-ecspresso/setup/#merge-the-pull-request

The initial step, to run CI and get the image to ECR works as expected. After that I've deployed the app, and it's running 🎉

The CD process fails at the Environment Info step with the error below (from github-action-interface-environment)

Run mkdir -p ./.environment_implementation/
  mkdir -p ./.environment_implementation/
  mv /home/runner/work/infrastructure-example-app-on-ecs/infrastructure-example-app-on-ecs/tmp.CWWaVA3DAq/.github/environments/ecspresso.yml ./.environment_implementation/action.yaml
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
mv: cannot stat '/home/runner/work/infrastructure-example-app-on-ecs/infrastructure-example-app-on-ecs/tmp.CWWaVA3DAq/.github/environments/ecspresso.yml': No such file or directory

These paths seem to make sense, as I can see the checkout step using it as a path as well.

I'm also seeing the latest commit messages on the infrastructure repo in the debug logs, hence I assume it's successfully checking out the repo.

Any clue what might be going on here? Or how I can further debug this?

[ronaldsteen]

Found it.. .yaml vs. .yml -- not sure if it was my typo or provided with the ref arch, or included in the template repo for the example app. I'll have another look at that tomorrow.

[Benbentwo]

Hey @ronaldsteen I just updated the app on ECS repository with some better docs. The real kicker here is the environment.yaml That needs to point to your either infra repo or another dir. it sounds like this was an issue with what we generated for you. I'll make sure that's fixed. Sorry for the hiccup

[ronaldsteen]

Ah, no, it originates from the app-on-ecs example -- that points to ecspresso.yml instead of ecspresso.yaml here.

I believe you should adjust that, since (almost) everywhere the .yaml extension is being used.

[ronaldsteen]

There's also a discrepancy for the app secrets between the guide on docs.cloudposse.com and the example repo.

https://github.com/cloudposse-examples/app-on-ecs/blob/main/.github/workflows/main-branch.yaml: PUBLIC_AND_PRIVATE_REPO_ACCESS_TOKEN_REPO

https://docs.cloudposse.com/layers/software-delivery/ecs-ecspresso/setup/#-add-the-example-app-secrets:
PRIVATE_CONFIG_READ_ACCESS

[ronaldsteen]

And another issue I hit:
https://github.com/cloudposse-examples/app-on-ecs/blob/main/.github/workflows/workflow-controller-draft-release.yml#L42 -- this is using release-drafter/release-drafter@v5. It's not able to access some releases API endpoint. Apparently Github changed things -> using v6 resolved the issue for me.

[Benbentwo]

Thanks, @ronaldsteen, I think I addressed the issues you brought up with this pull request. Please let me know if you find anything else. (also cloudposse-examples/app-on-ecs@8fb5830)

[GabisCampana]

@ronaldsteen can we close the loop on this? Or do you need further support here?