cloudposse/build-harness

build-harness gh actions doesn't work with act

3h4x opened this issue ยท 2 comments

3h4x commented

act should work with our gh actions in this repo.
It would simplify workflow and allow to test changes before pushing.
Especially this flag is interesting for continuous testing --watch - watch the contents of the local repo and run when files change

act             
[cloudposse-terraform-workflow/pre-commit] ๐Ÿš€  Start image=node:12.6-buster-slim
[lint/readme                             ] ๐Ÿš€  Start image=node:12.6-buster-slim
[cloudposse-terraform-workflow/pre-commit]   ๐Ÿณ  docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[lint/readme                             ]   ๐Ÿณ  docker run image=node:12.6-buster-slim entrypoint=["/usr/bin/tail" "-f" "/dev/null"] cmd=[]
[cloudposse-terraform-workflow/pre-commit]   ๐Ÿณ  docker cp src=/workspace/cloudposse.terraform-opsgenie/. dst=/github/workspace
[lint/readme                             ]   ๐Ÿณ  docker cp src=/workspace/cloudposse.terraform-opsgenie/. dst=/github/workspace
[lint/readme                             ] โญ  Run actions/checkout@master
[lint/readme                             ]   โœ…  Success - actions/checkout@master
[lint/readme                             ] โญ  Run cloudposse/build-harness@0.39.0
[lint/readme                             ]   โ˜  git clone 'https://github.com/cloudposse/build-harness' # ref=0.39.0
[cloudposse-terraform-workflow/pre-commit] โญ  Run actions/checkout@v1
[cloudposse-terraform-workflow/pre-commit]   โœ…  Success - actions/checkout@v1
[cloudposse-terraform-workflow/pre-commit] โญ  Run actions/setup-python@v1
[cloudposse-terraform-workflow/pre-commit]   โ˜  git clone 'https://github.com/actions/setup-python' # ref=v1
[lint/readme                             ]   โŒ  Failure - cloudposse/build-harness@0.39.0
Error: open /.cache/act/cloudposse-build-harness@0.39.0/action.yaml: no such file or directory

Sample action.yaml from actions-setup-python@v1 repo:

---
name: 'Setup Python'
description: 'Set up a specific version of Python and add the command-line tools to the PATH.'
author: 'GitHub'
inputs:
  python-version:
    description: "Version range or exact version of a Python version to use, using SemVer's version range syntax."
    default: '3.x'
  architecture:
    description: 'The target architecture (x86, x64) of the Python interpreter.'
    default: 'x64'
outputs:
  python-version:
    description: "The installed python version. Useful when given a version range as input."
runs:
  using: 'node12'
  main: 'dist/index.js'
branding:
  icon: 'code'
  color: 'yellow'

Thank you for reporting the issue! If you haven't already joined our slack community, then we invite you to do so.

This is a great place to get help and ask questions from our AMAZING community.

Slack Community

Nuru commented

Unfortunately, act is far from feature-complete, and it is not worth limiting ourselves to what act can handle.