Add instructions for license keys #86
Draft
+18
−6
Conversation
This file contains hidden or 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
Given we point to this changelog entry directly when upgrading to 26.0.0 in our docs, we should also add some information to update their license keys too.
SangJunBak
force-pushed
the
jun/add-instructions-for-license-key
branch
from
dbc9265 to
0041853
Compare
bobbyiliev
approved these changes
Nov 18, 2025
bobbyiliev
approved these changes
Nov 18, 2025
Collaborator
bobbyiliev
left a comment
bobbyiliev
left a comment
There was a problem hiding this comment.
Good catch! We would probably need the same for the other 2 modules as well:
- https://github.com/MaterializeInc/terraform-azurerm-materialize
- https://github.com/MaterializeInc/terraform-google-materialize
I'm happy to help out with those if you wish
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Given we point to this changelog entry directly when upgrading to 26.0.0 in our docs, we should also add some information to update their license keys too.