Add turso-jpedroh provider#95
Merged
vimtor merged 1 commit intoanomalyco:masterfrom May 5, 2026
Merged
Conversation
Contributor
Author
|
any updates on this @vimtor ? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The existing
tursoprovider appears to be outdated and lacks the right primitives for token generation (i.e. database auth tokens get recreated on every deployment, meaning tokens accumulate in Turso unnecessarily)The
jpedroh/tursopackage on the other hand seems to be more actively maintained (last version published ~6 months ago) and exposes a dedicated DatabaseToken resource, ensuring tokens are tracked in Pulumi state and survive across deployments.Happy to change the name of the package if needed!