Skip to content

Add ability to create missing intermediate paths when installing configuration files #3693

@evanorsouw

Description

@evanorsouw

Is your feature improvement request related to a problem? Please describe.

My use-case was the following;

  • extend tedge-configuration-plugin.toml with certificate of local local self-signed container registry.
[[files]]
type = "harbor-certificate"
path = "/etc/containers/certs.d/myregistry/ca.crt"
  • with podman installed, only the following path exists; /etc/containers/certs.d
  • problem now is that path component myregistry is application specific hence not known upfront.
    Therefor the deployment would fail with a file (path) not found exception.

Describe the solution you'd like
Proposed solution is to add the option makedirs to tedge-configuration-plugin.toml;

[[files]]
type = "harbor-certificate"
path = "/etc/containers/certs.d/<hostname>/ca.crt"
makedirs = true

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions