voxpupuli/crafty

CRAFTY - Containerized Resources And Funky Tools (in) YAML

crafty's Issues

remove raw.githubusercontent.com content from Dockerfiles

in the Dockerfile of puppetdb are references to raw.githubusercontent.com content.
we should fork the original or add it to the repos directly. to make sure it not suddenly vanishes from the web and breaks our ci.

see: https://github.com/voxpupuli/container-puppetdb/blob/main/puppetdb/Dockerfile#L60-L62

improve container tags

Hi,
just a proposal:

I saw that there are tags
["7.13.0","main-8","latest","main-7","v1.0.0-7","v1.0.0-8"]

but none of them is really explained in the README.md. I found some description in
https://github.com/voxpupuli/crafty/blob/main/docs/how-to-release.md

but it is rather confusing, because is says "don't use main-7, it can break any time", while "v1.0.0-7" is difficult to use, because it can change it's version number any time. Furthermore, there's no way to tell from the tags, that the containers are actually using 7.14.0 and 8.3.0 in build_versions.json.

My proposal is to follow current best practices and

• have tags like latest-7 , latest-8 , and latest, always pointing to the usable and recommended containers for production environments

• use v1.0.0-7 or main-7 as a development tag and not for productive use, because that v1.0.0 version number and branch name is important for your developers, but that tag should not keep changing all the time for production use.

• explain all these at prominent location in README.md

regards

make "how tags work" more visible

move the tagging section from the release howto into the readme, to have it more visible.
also applies to puppetserver and puppetdb.

Add puppetboard (using https)

update documentation

after #5 is solved in all repos we should update the docs

Add ARM platform

with the newest puppet OSS release we now ARM agents. the build should now be possible, because this was the only thing missing.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

docker-compose

puppet/oss/compose.yaml

• docker.io/postgres 16-alpine

---

• Check this box to trigger a request for Renovate to run again on this repository

Rework container tagging

atm i designed it this way, that the git tag is handed over to the docker build and is used internally to install the puppet version which matches to the git tag and this is then also apply as docker tag.

there is a edge case, when we rework our build or Dockerfile, that we might want to rebuild a container and the tag has to be move to another ref. this might be inconvenient to some people.

i think we could i rework like this:

• seperate docker tag and git tag
• add a version.json with the puppet releases and version

{
  "include": [
    {
      "release": 7,
      "version": "7.15.0"
    },
    {
      "release": 8,
      "version": "8.2.0"
    }
  ]
}

• add a github action to read this an prepare internal variables to hand this over to the container build
• use matrix build
• container tags could look like this 0.1.0-7 and 0.1.0-8 for marking them which puppet version is in it. Semver would allow to specify +build but this is not allowed by the container spec

🤔 💭

Add Helm chart

https://github.com/puppetlabs/puppetserver-helm-chart/ might be a good staring point.

push to docker.io

with the fixed version of gha-build-and-publish-a-container we should now be able to push also to docker.io / dockerhub.

postgresql has pgtrm missing

PuppetDB complains:

PostgreSQL extension `pg_trgm` missing.  Unable to create the recommend
ed pg_trgm indexes.
To fix, run this on the PuppetDB database as the database super user:
    CREATE EXTENSION pg_trgm;
Then restart PuppetDB.