feat: datasource for supabase_project_apikeys #212
Merged
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?
This PR introduces a new data source
supabase_project_apikeys
that allows retrieving API keys for a Supabase project. This is a read-only data source that provides access to both the anonymous and service role API keys.What is the current behavior?
Currently, there is no way to programmatically retrieve Supabase project API keys using Terraform. Users need to manually copy these values from the Supabase dashboard or store them separately.
What is the new behavior?
The new data source allows users to:
Example usage: