Make table name and index name a config value for PG backend #2465
+249
−40
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
|
Reminder for the PR assignee: If this is a user-visible change, please update the changelog as part of the PR. |
Signed-off-by: Taliesin Sisson <[email protected]>
taliesins
force-pushed
the
pg_table_name
branch
from
c18d1e3 to
f6947b3
Compare
|
This solves #2162 |
abstractionfactory
approved these changes
Feb 1, 2025
There was a problem hiding this comment.
Thank you for this @taliesins ! Normally, we like to discuss features in issue before accepting a PR, but this seems fairly straight forward. I'm queueing this for the core team to discuss, but otherwise LGTM!
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.
Make it possible to specify the table name and index name when using PG backend.
This makes it easier to use PG backend provider for scenarios such as using Terragrunt with convention based state storage per a
terragrunt.hclfile by providing an additional layer of grouping.Having many tables vs many schemas could be preferred by some users and the tools they use too.