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

📖 Fix outdated links in implementers guide #6166

Merged

Conversation

killianmuldoon
Copy link
Contributor

Signed-off-by: killianmuldoon [email protected]

What this PR does / why we need it:
Fixes outdated links in the book, add required information to recent versions of the book and removing references to old book versions.

c/f #6028

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 17, 2022
Copy link
Contributor Author

@killianmuldoon killianmuldoon left a comment

Choose a reason for hiding this comment

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

I plan to create a larger issue around updating the implementers guide in the book. Thanks to @anusha94 @richardcase for giving me some pointers on where it can improve. I'd appreciate your reviews here too if you have the time.

@killianmuldoon killianmuldoon changed the title 📖 Fix outdated links in implementers guide to replace links 📖 Fix outdated links in implementers guide Feb 17, 2022
@@ -71,6 +71,8 @@
- [Create API](./developer/providers/implementers-guide/create_api.md)
- [Controllers and Reconciliation](./developer/providers/implementers-guide/controllers_and_reconciliation.md)
- [Building, Running, Testing](./developer/providers/implementers-guide/building_running_and_testing.md)
- [Webhooks](./developer/providers/webhooks.md)
- [Provider contracts](./developer/providers/contracts.md)
Copy link
Member

Choose a reason for hiding this comment

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

I know this isn't up to this PR but i really found the menu below Provider implementers confusing
wondering if we can reorg/make things a little bit simpler. some ideas:

  • group migration guides
  • drop double nesting Provider implementers/Implementer's Guide
  • move webhooks aftre API
  • move contract somewhere up in the sequence and nest cluster infrastructure, machine infrastructure and bootstrap

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've done all of this except for dropping the double nesting. I think it's important for the structure right now as the implementers guide is a standalone step-by-step guide.

docs/book/src/developer/providers/contracts.md Outdated Show resolved Hide resolved
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 21, 2022
Copy link
Member

@sbueringer sbueringer 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 very much for tackling this!

Especially as it's not one of our most glamorous issues :)

A few nits

- [Cluster Infrastructure](./developer/providers/cluster-infrastructure.md)
- [Machine Infrastructure](./developer/providers/machine-infrastructure.md)
- [Bootstrap](./developer/providers/bootstrap.md)
- [Version migration](./developer/providers/version-migration.md)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- [Version migration](./developer/providers/version-migration.md)
- [Migration guides](./developer/providers/version-migration.md)

nit, if you want (same for the file name)

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 think version migration is clearer and more specific here, but if there's a call to use the more generic title I'll change it.

Copy link
Member

Choose a reason for hiding this comment

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

Just keep it as is. Version migration just sounded strange to me, but my entire understanding of the english language is subjective :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As is mine!

Copy link
Member

@sbueringer sbueringer Feb 21, 2022

Choose a reason for hiding this comment

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

I hope yours is better than mine and you correct the nits I drop on PRs of other folks if they are just too wrong :) (btw :) )

docs/book/src/developer/providers/version-migration.md Outdated Show resolved Hide resolved
docs/book/src/developer/providers/contracts.md Outdated Show resolved Hide resolved
docs/book/src/developer/providers/webhooks.md Outdated Show resolved Hide resolved
@sbueringer
Copy link
Member

Thx!
lgtm pending squash

@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 Feb 21, 2022
@fabriziopandini
Copy link
Member

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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 Feb 22, 2022
@k8s-ci-robot k8s-ci-robot merged commit 2056db8 into kubernetes-sigs:main Feb 22, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.2 milestone Feb 22, 2022
@sbueringer
Copy link
Member

@killianmuldoon @fabriziopandini Should we backport?

@fabriziopandini
Copy link
Member

I don't think so.
These are docs for developers and one way or the other they need to look at main

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/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.

4 participants