#release-engineering - November 2021

anyone run into issues with github-actions and using an env value that starts with https://? e.g.

    env:
      REPO_ENDPOINT: 'https://...'

it keeps stripping the https:// from the env in the log, but i can't find any docs on that behavior. and i'm pretty sure the yaml is fine?

hi folks, has anyone managed to get an idea the cost between GHA/ CodeFresh & Spacelift? Asking as i've been using GHA which is dead cheap however when i'm looking at the others i see 250$/m and that limited to 5 users.

hi folks, in one of the office hours or other videos it was mentioned a CD pattern using GHA instead of codefresh/ spacelift. If i remember correctly it was said that a pattern of below could be achieved:

CI:

• TF config or modules in one git repo
• GHA to build and upload artefacts - ie lambda docker/ layer/ zip file to S3/ ECR (not use tf lambda modul to deal with packaging
CD:

• a different / standalone git repo which will run TF plan/ apply to v envs.
Q:

What i don't get how the source repos (in case of poly-repo where various TF modules are scattered in N GH org repos) will:

• be synced to CD git repo? What sort of dir structure layout will be on the CD repo to cover for multiple deployments for different root modules ?
• any metadata consumed by CD and generated by CI - how will that be available ? i.e each lambda zip file or docker image / or TF code will generate a new tag/ release ... that needs to be consumed somehow by CD GHA workflows no ?
anyway i forgot who made the claim about using GHA as CD, will love to understand more the pattern