-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendor c/common: appendable containers.conf strings, Part 1 #5101
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Ephemeral COPR build failed. @containers/packit-build please check. |
2 similar comments
Ephemeral COPR build failed. @containers/packit-build please check. |
Ephemeral COPR build failed. @containers/packit-build please check. |
@nalind @rhatdan @flouthoc PTAL |
@vrothberg you can start dancing. |
This change is the first step of integrating appendable string arrays into containers.conf and starts with enabling the `Env`, `Mounts`, and `Volumes` fields in the `[Containers]` table. Both, Buildah and Podman, read (and sometimes write) the fields of the `Config` struct at various places, so I decided to migrate the fields step-by-step. The ones in this change are most critical ones for customers. Once all string slices/arrays are migrated, the docs of containers.conf will be updated. The current changes are entirely transparent to users. [NO NEW TESTS NEEDED] Signed-off-by: Valentin Rothberg <[email protected]>
Updated ✔️ |
/lgtm |
This change is the first step of integrating appendable string arrays into containers.conf and starts with enabling the
Env
,Mounts
, andVolumes
fields in the[Containers]
table.Both, Buildah and Podman, read (and sometimes write) the fields of the
Config
struct at various places, so I decided to migrate the fields step-by-step. The ones in this change are most critical ones for customers. Once all string slices/arrays are migrated, the docs of containers.conf will be updated. The current changes are entirely transparent to users.What type of PR is this?
/kind feature
What this PR does / why we need it:
See above.
How to verify it
See tests in containers/common#1707.
Which issue(s) this PR fixes:
First pass on https://issues.redhat.com/browse/RUN-1934.
Special notes for your reviewer:
Does this PR introduce a user-facing change?
See above.