azavea / azavea/docker-terraform

Build a 0.x series image that always is on the latest patch release

Open
#19 0 comments 0 reactions 0 assignees View on GitHub
actionable backlog operations
Dominant language
Shell
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Description

It feels like the cadence of [Terraform releases](https://github.com/hashicorp/terraform/releases) is increasing. We haven't adopted 0.13 and the first 0.14 beta [was released](https://github.com/hashicorp/terraform/releases/tag/v0.14.0-beta1).

We usually add an image here for the latest Terraform version when we're starting a project. This leads to some weird stuff like gaps of 10 releases between images we maintain.

I don't see any reason why we wouldn't want all our projects to be on the latest patch release. I think we should publish a `quay.io/azavea/terraform:0.xx` image tag that always resolves to the latest patch release for a Terraform series. This would help us keep up, at least within a specific series.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the Terraform releases linked in the issue and inspecting how this repository currently builds and publishes versioned images. Determine how a 0.xx tag could track the latest patch release in that series, then verify that the published tag resolves correctly as new patch releases appear.

Written by the indexing model from the issue text.

Assessment

Tech stack
terraform
Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.