Skip to content
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

Kube Play - Support multi-doc YAML files for configmap argument #18538

Merged

Conversation

ygalblum
Copy link
Contributor

Read the entire YAML file in case of a multi-doc file Adjust the unit test
Add a system test
Add comment in the man page

Resolves: #18537

Does this PR introduce a user-facing change?

Yes

Kube Play - Support multi-doc YAML files for configmap argument

@openshift-ci openshift-ci bot added release-note approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 11, 2023
@ygalblum ygalblum force-pushed the play-multiple-configmaps branch from 2c92915 to 92f3681 Compare May 11, 2023 09:50
Comment on lines 707 to 709
run_podman kube play --configmap=$configmap_file $pod_file
run_podman logs test_pod-server
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to do a podman wait in between to prevent flakes, play just start we do not know if the echo command was executed by the time we run logs. We actually have to make sure the container exited before running logs.
cc @edsantiago

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Read the entire YAML file in case of a multi-doc file
Adjust the unit test
Add a system test
Add comment in the man page

Signed-off-by: Ygal Blum <[email protected]>
@ygalblum ygalblum force-pushed the play-multiple-configmaps branch from 92f3681 to 26f1e95 Compare May 11, 2023 10:13
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 11, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 11, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vrothberg, ygalblum

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rhatdan
Copy link
Member

rhatdan commented May 11, 2023

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2023
@openshift-merge-robot openshift-merge-robot merged commit 20b15f0 into containers:main May 11, 2023
@ygalblum ygalblum deleted the play-multiple-configmaps branch May 11, 2023 14:00
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

podman kube play reads only the first entity in the configmap files passed with --configmap
5 participants