Skip to content

Conversation

@paigecalvert
Copy link
Contributor

@paigecalvert paigecalvert commented Nov 1, 2024

Beta topic for Install Types: https://deploy-preview-2801--replicated-docs.netlify.app/vendor/licenses-install-types

Update the existing "Creating and Managing Customers" topic so that it's generic enough to apply to any vendor: https://deploy-preview-2801--replicated-docs.netlify.app/vendor/releases-creating-customer

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Nov 1, 2024
@netlify
Copy link

netlify bot commented Nov 1, 2024

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 2a5f43c
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs/deploys/67295a36d9ab930008c20c0e
😎 Deploy Preview https://deploy-preview-2801--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@netlify
Copy link

netlify bot commented Nov 1, 2024

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 2a5f43c
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs-upgrade/deploys/67295a368c5ac0000832b0ca
😎 Deploy Preview https://deploy-preview-2801--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

</table>

1. (Optional) For **Custom fields**, configure any custom fields that are available for your Replicated application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
1. Enable any of the license options that you want to support for the customer. For more information about the built-in options, see [Built-in License Fields](licenses-using-builtin-fields).
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ Removes the table that was here that listed out the built-in options in favor of just pointing people to the main "Built-In License Field" topic. Probably should have been doing this anyway to avoid the info getting out of sync

@@ -0,0 +1,58 @@
# Managing Install Types for a License (Beta)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ Adds a separate topic about install types

@paigecalvert paigecalvert marked this pull request as ready for review November 4, 2024 23:02
@paigecalvert paigecalvert requested a review from a team as a code owner November 4, 2024 23:02
</table>

1. (Optional) For **Custom fields**, configure any custom fields that are available for your Replicated application. For more information about how to create custom fields for your application, see [Managing Custom License Fields](licenses-adding-custom-fields).
1. Enable any of the available options for the customer. For more information about the license options, see [Built-in License Fields](/vendor/licenses-using-builtin-fields). For more information about enabling install types, see [Managing Install Types for a License (Beta)](/vendor/licenses-install-types).
Copy link
Contributor Author

Choose a reason for hiding this comment

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

^ updated this step to be more generic and just added xrefs so people can get more info about their specific options

@paigecalvert paigecalvert merged commit 55940b8 into main Nov 13, 2024
5 checks passed
@paigecalvert paigecalvert deleted the 115325 branch November 13, 2024 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants