Skip to content

fix: allow to edit secrets/configmaps in multi-resource yaml documents (#852) #853

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

Merged
merged 3 commits into from
Mar 28, 2025

Conversation

adietish
Copy link
Collaborator

@adietish adietish commented Mar 3, 2025

@adietish adietish self-assigned this Mar 3, 2025
@adietish adietish force-pushed the issue-852 branch 6 times, most recently from a8e288d to 9b072ad Compare March 4, 2025 16:25
@adietish adietish changed the title fix: allow to edit secrets/configmaps in multi-resource documents (#852) fix: allow to edit secrets/configmaps in multi-resource yamldocuments (#852) Mar 6, 2025
@adietish adietish changed the title fix: allow to edit secrets/configmaps in multi-resource yamldocuments (#852) fix: allow to edit secrets/configmaps in multi-resource yaml documents (#852) Mar 6, 2025
@adietish
Copy link
Collaborator Author

adietish commented Mar 6, 2025

multi-resource json files are not supported yet. See #855

@adietish adietish marked this pull request as ready for review March 13, 2025 10:29
@adietish adietish requested a review from sbouchet March 13, 2025 10:30
Signed-off-by: Andre Dietisheim <[email protected]>
@adietish
Copy link
Collaborator Author

@msivasubramaniaan: glad that your testing result was +1. Can you please approve the PR so that I can merge it? thanks!

Copy link

@msivasubramaniaan msivasubramaniaan left a comment

Choose a reason for hiding this comment

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

LGTM.

@adietish adietish merged commit 58e240e into redhat-developer:main Mar 28, 2025
10 of 18 checks passed
@adietish adietish deleted the issue-852 branch March 28, 2025 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants