cloudfoundry / cloudfoundry/runtime-ci

check-certs task should automatically delete expired BOSH director and jumpbox certificates

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9
Forks
16
Avg merge
7d 10h
Merged PRs (30d)
10

Description

We want to enhance the "check-certs" task so that it automatically deletes expired bbl certificates, according to the manual procedure we currently apply: https://github.com/cloudfoundry/relint-envs/tree/main#certificate-renewal.

The Concourse task could get a new parameter FILES_TO_AUTOMATICALLY_RENEW with a list of director and jumpbox vars store files, e.g.:

- environments/test/hermione/bbl-state/vars/director-vars-store.yml
- environments/test/hermione/bbl-state/vars/jumpbox-vars-store.yml
- environments/test/trelawney/bbl-state/vars/director-vars-store.yml
- environments/test/trelawney/bbl-state/vars/jumpbox-vars-store.yml
(...)

The cleaned up vars-store files would then be committed to the "relint-envs" repo. The next "update-infrastructure" job will recreate the missing certificates.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the check-certs Concourse task and the certificate-renewal procedure linked in the issue. Review the listed director-vars-store.yml and jumpbox-vars-store.yml files and determine how the new FILES_TO_AUTOMATICALLY_RENEW parameter should apply to them. Done means expired certificates are removed, the cleaned files can be committed to relint-envs, and the next update-infrastructure job recreates them.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.