Skip to content

Use Sprig template functions and add asLabelValue function #2038

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 1 commit into from
Feb 20, 2025
Merged

Use Sprig template functions and add asLabelValue function #2038

merged 1 commit into from
Feb 20, 2025

Conversation

fahhem
Copy link
Contributor

@fahhem fahhem commented Jan 29, 2025

Fixes #2033

@k8s-ci-robot k8s-ci-robot added do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 29, 2025
@k8s-ci-robot
Copy link
Contributor

Welcome @fahhem!

It looks like this is your first PR to kubernetes-sigs/node-feature-discovery 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/node-feature-discovery has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @fahhem. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 29, 2025
Copy link

netlify bot commented Jan 29, 2025

Deploy Preview for kubernetes-sigs-nfd ready!

Name Link
🔨 Latest commit b0dbd11
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-nfd/deploys/67b5a9e34c909c000853a332
😎 Deploy Preview https://deploy-preview-2038--kubernetes-sigs-nfd.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/invalid-commit-message Indicates that a PR should not merge because it has an invalid commit message. label Jan 29, 2025
Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

Thank you @fahhem for the contribution. That was quick 😄 A few comments below.

Also, could you update the documentation (https://kubernetes-sigs.github.io/node-feature-discovery/v0.16/usage/customization-guide.html#templating) to mention that the sprig funcs are supported?

@marquiz
Copy link
Contributor

marquiz commented Jan 30, 2025

/cc @ArangoGutierrez

@marquiz
Copy link
Contributor

marquiz commented Jan 30, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 30, 2025
@fahhem
Copy link
Contributor Author

fahhem commented Jan 30, 2025

Looks like all the tests pass now!

Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

@fahhem thanks for the update, looks very good now, just two small nits/suggestions below. I think you could also squash the commits into one.

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jan 31, 2025
@fahhem
Copy link
Contributor Author

fahhem commented Jan 31, 2025

/retest

@fahhem fahhem requested a review from marquiz February 1, 2025 00:43
@fahhem
Copy link
Contributor Author

fahhem commented Feb 5, 2025

I don't understand why that test is failing, there's no tracebacks or anything, it just dies after 2 hours

@marquiz
Copy link
Contributor

marquiz commented Feb 5, 2025

I don't understand why that test is failing, there's no tracebacks or anything, it just dies after 2 hours

Ach, that is some flake in the cross-build (arm64) builds that I'm not sure why it gets stuck. Just need to re-test until it succeeds
/retest

@marquiz
Copy link
Contributor

marquiz commented Feb 5, 2025

Thanks @fahhem for the update. I put my review comment in a form of a PR
https://github.com/SonicInfra/node-feature-discovery/pull/1

If you think that is ok you can just squash it into your commit.

@fahhem
Copy link
Contributor Author

fahhem commented Feb 6, 2025

Thanks! I'll squash them now

@fahhem
Copy link
Contributor Author

fahhem commented Feb 6, 2025

/retest

Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

Nice work, looks good to me now

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2025
@marquiz
Copy link
Contributor

marquiz commented Feb 6, 2025

/assign @ArangoGutierrez

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Feb 16, 2025
@marquiz
Copy link
Contributor

marquiz commented Feb 19, 2025

@fahhem could you do a (clean) rebase the patch on top of master to get rid of the merge commit?

@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 19, 2025
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 19, 2025
@fahhem
Copy link
Contributor Author

fahhem commented Feb 19, 2025

/retest

@fahhem
Copy link
Contributor Author

fahhem commented Feb 19, 2025

@marquiz okay, done!

Copy link
Contributor

@ArangoGutierrez ArangoGutierrez left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 20, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 1717057feca8b4cf23c1e1948edb07eaf237ebbf

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArangoGutierrez, fahhem, marquiz

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:
  • OWNERS [ArangoGutierrez,marquiz]

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 merged commit b62e7c1 into kubernetes-sigs:master Feb 20, 2025
12 checks passed
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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use Sprig template functions
5 participants