feat: update secretTemplate documentation#634
feat: update secretTemplate documentation#634jetstack-bot merged 5 commits intocert-manager:release-nextfrom jonathansp:master
Conversation
|
Hi @jonathansp. Thanks for your PR. I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/assign @jakexks |
|
/ok-to-test Thanks for all your work on this @jonathansp |
| If `secretTemplate` is present, annotations and labels set in this property | ||
| will be copied over to `example-com-tls` secret. Both properties are optional. |
There was a problem hiding this comment.
Just wondering, how do we let people know that this is a feature that only exists since 1.5? The user would have to look for differences between 1.4 and 1.5 to find that out.
I'd go with smth like:
| If `secretTemplate` is present, annotations and labels set in this property | |
| will be copied over to `example-com-tls` secret. Both properties are optional. | |
| If `secretTemplate` _(since cert-manager 1.5)_ is present, annotations and labels set in this property | |
| will be copied over to `example-com-tls` secret. Both properties are optional. |
@irbekrm what do you think? 😅
There was a problem hiding this comment.
Our docs are versioned so I don't think this is too much of a concern.
There was a problem hiding this comment.
@JoshVanL I find it very frustrating to have to select one by one the documentation versions to find when a feature was introduced and know if your version of cert-manager works with that feature, since Google always returns the latest version of the pages.
I am often in the situation where I start using a feature and realize later on that the feature was introduced in a later version. This happened 3 times in the last month while using Traefik. I just wish they had a tiny note on every Ingress annotation that reminds me "when" this annotation was added.
There was a problem hiding this comment.
I guess we may want to merge this into release-next branch, not into master though?
There was a problem hiding this comment.
I've just added a release note based on the PR description and code comments, let me know if it needs to be rewritten. @benlangfeld I took the liberty to add your name to the contributors' list above.
There was a problem hiding this comment.
Looks like our stupid spellchecker doesn't like the github usernames. You'll have to add them to the .spelling file. See https://github.com/cert-manager/website/blame/master/.spelling#L265
There was a problem hiding this comment.
Usernames added to .spelling.
There was a problem hiding this comment.
@jonathansp I'm flattered, but I didn't do anything nearly worth being included in a list of contributors :)
|
✔️ Deploy Preview for cert-manager-website ready! 🔨 Explore the source changes: 66a75bd 🔍 Inspect the deploy log: https://app.netlify.com/sites/cert-manager-website/deploys/610a813736af840008b14b1b 😎 Browse the preview: https://deploy-preview-634--cert-manager-website.netlify.app |
wallrj
left a comment
There was a problem hiding this comment.
@jonathansp Please update the PR to be merged in to the release-next branch (as @irbekrm mentioned above)
That's the branch containing the documentation and release notes for the upcoming 1.5 release, which will be the first release containing your secret template work.
Thanks.
|
@jonathansp Also please update the release-notes page with a paragraph about the new secret template feature. Thanks. |
|
@jonathansp Do you think you could click "Edit" on the PR and select "release-next" instead of "master" as the base branch? That would probably also require a rebase onto release-next. Please let me know if you need help with that. |
Sorry @maelvls, couple of meetings this morning. Will do. |
Signed-off-by: jonathansp <jonathansimonprates@gmail.com>
wallrj
left a comment
There was a problem hiding this comment.
Thanks again. This looks great.
/lgtm
/approve
| Special thanks to the external contributors who contributed to this release: | ||
| - TODO | ||
|
|
||
| * [@jonathansp](https://github.com/jonathansp) |
|
/retest |
Signed-off-by: jonathansp <jonathansimonprates@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: jonathansp, wallrj The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: jonathansp jonathansimonprates@gmail.com
Update docs to include cert-manager/cert-manager#3828 feature.
cc @maelvls