controller-gen unable to set file headers

[chrislovecnm]

This I believe is a feature request. It would be awesome to have controller-gen output file headers when you generate yaml files with the clip. When generating go code you are able to set a header file, but when you generate yaml it seems that does not work.

When providing the following options the yaml files do not contain a header.

controller-gen object:headerFile=./hack/boilerplate/boilerplate.yaml.txt rbac:roleName=manager-role webhook paths="./..." output:crd:artifacts:config=config/crd/bases

Maybe I am missing something.

[coro]

I'd agree with this, would love to see this feature. We have a requirement to include license NOTICE headers in even our generated YAML, and this would allow us to perform this without manually injecting it after every run of controller-gen.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

[justinsb]

/reopen

Should we turn off the robot?

[k8s-ci-robot]

@justinsb: Reopened this issue.

In response to this:

/reopen

Should we turn off the robot?

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.