Skip to content

Make sure certificate handling is idempotent and reacts to changes #35

Closed
@widhalmt

Description

@widhalmt

We're creating a lot of certificates via different ways. And we're copying them via different hosts. We need to make very sure that we have a stable and reliable way to recreate certificates and even the whole CA. We need all versions: Just one certificate, all files for one host, whole CA.

Make especially sure that creating different formats like pkcs8 for Logstash is not broken because e.g. we only check for presence of the file when deciding whether we need to recreate it or not.

There are a few ideas about how to handle this:

  • Deleteing temporary files right after transport
  • Using unique temporary directories or filenames which won't be reused in the next run
  • Checking whether the generated targets still match the source

Metadata

Metadata

Labels

featureNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions