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

Update AWS Provisioner docs w/ proper tag examples #1402

Merged
merged 4 commits into from Feb 24, 2022

Conversation

bwagner5
Copy link
Contributor

@bwagner5 bwagner5 commented Feb 22, 2022

1. Issue, if available:
#1310

2. Description of changes:

  • Update AWS Provisioner docs to:
    • use karpenter.sh/discovery tags in examples
    • use proper tag Name example (it was using the id rather than name)
    • perma link code link to version and remove line number anchor

3. How was this change tested?

  • Netlify preview on PR

4. Does this change impact docs?

  • Yes, PR includes docs updates
  • Yes, issue opened: link to issue
  • No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@netlify
Copy link

netlify bot commented Feb 22, 2022

✔️ Deploy Preview for karpenter-docs-prod ready!

🔨 Explore the source changes: ecf2b0e

🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/6215594575c7d30007bcc5a2

😎 Browse the preview: https://deploy-preview-1402--karpenter-docs-prod.netlify.app

@bwagner5 bwagner5 changed the title update AWS Provisioner docs w/ proper tag examples [WIP] update AWS Provisioner docs w/ proper tag examples Feb 22, 2022
@bwagner5 bwagner5 changed the title [WIP] update AWS Provisioner docs w/ proper tag examples Update AWS Provisioner docs w/ proper tag examples Feb 22, 2022
@@ -0,0 +1 @@
/{{ replace (chomp (delimit (first 2 (split .Page.RelPermalink "/")) "" "")) "preview" .Page.Site.Params.github_branch }}/
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we leave the slashes outside, e.g. /{{< githubRelRef > }}/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can, the reason I have it like this is to match the {{< relref >}} that we use for the versioned links for docs pages which includes the slashes.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ahh gotcha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants