feat: resource for project apikey #256
Merged
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
tontonrally
force-pushed
the
main
branch
2 times, most recently
from
244a3aa to
6357dae
Compare
savme
reviewed
Nov 29, 2025
Collaborator
savme
left a comment
savme
left a comment
There was a problem hiding this comment.
Thank you for the contribution, @tontonrally - this looks great!
I just have a couple of minor comments/questions
savme
reviewed
Dec 4, 2025
savme
approved these changes
Dec 4, 2025
Collaborator
savme
left a comment
savme
left a comment
There was a problem hiding this comment.
Great addition to the provider 👍
Thanks for contributing this, @tontonrally!
* (apikeys_data_source.go): added support for apiKeys * (apikey_resource.go): added support for apikey resource (create, update, delete & import) * (apikey_resource_test.go): added tests for apikey resource * generate docs
chore: generic NullableToString. Handles enum as well
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.
What kind of change does this PR introduce?
feature
What is the current behavior?
apikeys are not listed in datasource
apikey are not supported, we cannot create/delete these type of resources
What is the new behavior?
apikeys are listed in the supabase_apikeys datasource
apikey resource is supported, we can create secret apikey like
Additional context
I needed that feature on my own project and I decided to contribute.
Not sure about the update of keys as it is not supported in the UI but available on the supabase go sdk.