Add error log when trial licenses are being used #3053
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Most of our docs and pages for enterprise licenses are heavily pushing for generating trial licenses. However, we cannot support trial licenses in connect, and therefore these licenses are considered invalid for the purposes of running enterprise connect features.
This leaves us vulnerable to a poor user experience where a user tries to run enterprise features, is told by RPCN to visit https://cloud.redpanda.com/try-enterprise, where we then encourage them to create a trial (for Redpanda proper). When a user attempts to run the trial we will tell them it's invalid from Connect.
In order to at least clarify what is happening to the user I've added an explicit error log that notes the license is a trial, not a full license that connect will recognize.