microsoft / microsoft/AzureTRE
Change 'Renew Lets Encrypt' Action to use Dev Container
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Change the 'Renew Lets Encrypt' GitHub Action yaml to run make lets encrypt within the standard TRE Dev Container (as other GitHub Actions do).
This means the command will run with the pinned versions of tools such as az and terraform and not experience issues (such as #4594) when GitHub updates the versions in the standard ubuntu-latest build.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
First inspect the GitHub Actions workflow for “Renew Lets Encrypt” and compare it with other workflows that use the standard TRE Dev Container. Update that workflow so the existing make lets encrypt command runs in the container, then verify that the pinned az and terraform versions are used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, github-actions, terraform
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100