-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 generated annotation #354
Conversation
add generated annotation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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/test-infra repository. I understand the commands that are listed here. |
I just signed the CLA (again?) And I've already signed on behalf of my company so I think I'm good now? |
/check-cla |
Looks like this PR is a little premature, I'll wrap it up tomorrow |
/lgtm |
/hold test needs fixing. Also, how about adding a new field to the kustomization.yaml file to allow people to add the annotation optionally rather than hardcoding it. |
@monopole I thought about that--I think it might be a good idea to add both, allowing users to overwrite the value of the default. Sound Ok? |
Ah wait, @monopole, we can do this already with |
passing tests
…ions Feat/labels and annotations
New changes are detected. LGTM label has been removed. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pnovotnak If they are not already assigned, you can assign the PR to them by writing 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 |
Ok, tests are fixed, and I added a testcase for both configmaps and secrets that are not generated (neither should have the generated annotation applied). I think this is ready to go if someone has time to review |
Hi, sorry about the delay. We think this is a good feature, but would prefer to make it strictly optional. @Liujingfang1 and i talked, and think it would be good to add a field at the root level - i.e. called, say. E.g.
This PR would get smaller, because there'd be no need to change the data for all the tests. Just add new tests. |
@pnovotnak What's the progress on this? Do you need any help? |
@Liujingfang1 Sorry! I hadn't been keeping up with my GH notifications. I'll make the change today |
I added |
closes #353
Add a common label to generated objects, so that they may be identified as such. I don't think this requires documentation--the first place someone will probably look for this information on generated objects themselves.