| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Change-Id: Iaddda80bc78bf727d8a2835d1528f49639aa87a0
Signed-off-by: Michal Arbet <michal.arbet@ultimum.io>
|
|
|
|
This adds support for the ACME dns-01 challenge while keeping http-01
the default. A new --challenge option (default http-01) selects the
challenge type. When dns-01 is selected, --dns-provider names any DNS
provider compiled into the bundled lego binary, and an optional
--dns-additional-opts passthrough forwards extra lego DNS flags (such as
--dns.resolvers or --dns.propagation-disable-ans) for environments where
the authoritative name server propagation check cannot be performed.
Provider credentials are supplied via --env-file: lego DNS providers
read credentials only from environment variables, so the wrapper
exports the file's contents before lego runs. The file is parsed like
docker --env-file: literal KEY=VALUE pairs split on the first '=',
comments and blank lines ignored, values taken verbatim and never
executed as shell. Selecting dns-01 without --dns-provider fails fast.
Co-Authored-By: Premysl Kouril <premysl.kouril@ultimum.io>
Assisted-By: Claude Code
Change-Id: I61dc5e3f399f6eec02475c7b90e0f41c85c6093c
Signed-off-by: Timon Schnell <timon.schnell@btc-it-services.com>
Signed-off-by: Jan Horstmann <horstmann@osism.tech>
|
|
Repos marked build_only: true are backed up before handle_repos()
overwrites them and restored at the end of each image build, so CI
mirror URLs are not baked into the final image.
The cleanup RUN was injected into every Dockerfile, not just images
that called handle_repos() for those repos. Child images with no
backup fell through to "rm -f", deleting the inherited repo file
(e.g. debian.sources in bifrost-base, breaking cpio install).
Fix by adding a {repo}.enabled sentinel that handle_repos creates
when it processes a build_only repo, making the cleanup conditional
on that sentinel.
Change-Id: Ie5b9970a4575b6258dc238059d3f33ddfe155789
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
[tool.setuptools.data-files] does not support recursive directory
installation. The old setup.cfg [files] worked because PBR's
FilesConfig.expand_globs() used os.walk() to expand docker/*, but
this hook is not triggered by the pbr.build PEP-517 backend.
Move docker/ into kolla/ and use [tool.setuptools.package-data]
instead. Update kolla_worker._get_images_dir() to check the kolla
package directory first so both editable and regular installs work.
Change-Id: I4fc452c03740ef22ebbb4e8d0d86c4f4783e2d09
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
