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

🌱 Add test-extension patch artifacts to git ignore #7137

Conversation

killianmuldoon
Copy link
Contributor

Signed-off-by: killianmuldoon [email protected]

Add the yaml-e files generated with the test extension to the .gitignore.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 31, 2022
@killianmuldoon killianmuldoon changed the title Add test-extension patch artifacts to git ignore 🌱 Add test-extension patch artifacts to git ignore Aug 31, 2022
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 31, 2022
test/e2e/data/test-extension/deployment.yaml
test/extension/config/default/extension_image_patch.yaml-e
test/extension/config/default/extension_pull_policy.yaml-e

Copy link
Member

Choose a reason for hiding this comment

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

Just to clarify those files are not generated. They are some side-effect of afaik an editor (or maybe something else?).

I also have them from time to time, but only very rarely (and up until now I only had them for the files which are overwritten when running make docker-build, e.g. config/default/manager_image_patch.yaml)

Or?

Copy link
Member

@sbueringer sbueringer Aug 31, 2022

Choose a reason for hiding this comment

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

Given the way we change those files I would guess some tmp files of sed

xref: https://stackoverflow.com/questions/34533893/sed-command-creating-unwanted-duplicates-of-file-with-e-extension

Just a random finding on stackoverflow, but maybe there's a way to fix our sed calls that those files never occur

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was trying to track down what created them - I assume it's either kustomize or intellij, but I still haven't figured it out 🙁.

Good to have them in the .gitignore anyway IMO - also have them for the manager*.yaml-e already.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good find! This seems to be an OSX issue, and I think it's well enough taken care of by adding it to gitignore. Might be a good idea for me to add gnu sed to my env though!

Copy link
Member

@sbueringer sbueringer Aug 31, 2022

Choose a reason for hiding this comment

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

I'm fine with just adding them, let's just do it for all (as you suggested) and let's add a short comment where those files are ~ coming from.

This should only affect ~ two files per manager which should be the ones we run sed / that make target on

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How does the latest version look?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Confirmed btw that gnu-sed on MacOS doesn't have this issue. Our flags for sed aren't fully portable. I'll create an issue for that to track it, but it's low impact and priority imo

Copy link
Member

Choose a reason for hiding this comment

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

How does the latest version look?

Perfect. I didn't know we already had the gitignore for manager YAMLs. But explains why you're only seeing that issue now

@killianmuldoon killianmuldoon force-pushed the gitignore/add-test-extension branch from 55e0436 to 9ea5cb5 Compare August 31, 2022 12:06
@killianmuldoon killianmuldoon force-pushed the gitignore/add-test-extension branch from 9ea5cb5 to f2aabd2 Compare August 31, 2022 12:06
@sbueringer
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 31, 2022
@sbueringer
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 1, 2022
@k8s-ci-robot k8s-ci-robot merged commit e468cab into kubernetes-sigs:main Sep 1, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.3 milestone Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants