Skip to content

Conversation

michaellzc
Copy link
Member

@michaellzc michaellzc commented May 3, 2025

ref cyrilgdn#210

use cases:

When a role is managed externally, e.g., google_sql_user, and such provider does not provide ability to customize role attribute. postgresql provider that has direct connection to the db host can be used to perform such automation.

this PR introduced a new postgresql_role_attribute resource to manage role attribute without holding on to the role itself.

design decisions:

  • it's non-authoritative, unlike postgresql_role. it does not assume any default value for the attribute, and ignore any nil attribute.
  • on destroy, it will simply orphaned the attribute without attempting to revert it in any way. this is intentional to avoid the headache of conflicted resources.

@michaellzc michaellzc force-pushed the mlzc/add-role-attribute-resource branch 3 times, most recently from 2a295b3 to 292ca7b Compare May 3, 2025 04:42
@michaellzc michaellzc force-pushed the mlzc/add-role-attribute-resource branch from 292ca7b to a7fe7c7 Compare June 4, 2025 17:53
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant