[ADAP-474] [Feature] Accept users, groups, or roles in grants config on resource

[stevenayers-tvx]

Is this a new bug in dbt-redshift?

• I believe this is a new bug in dbt-redshift
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

After specifically creating the group finance_department in Redshift, I cannot use it as a grantee in the grant config.

I can see the group when I run SELECT * FROM pg_group

models:
  - name: specific_model
    config:
      grants:
        select: ['finance_department']

Error: user "finance_department" does not exist

Expected Behavior

Grantee syntax says groups, not just users, should be accepted: https://docs.getdbt.com/reference/resource-configs/grants#common-syntax

Steps To Reproduce

1. Create a group in redshift
2. Add to a grants config on a model

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-redshift:

Additional Context

No response

[dbeatty10]

Thanks for following up @stevenayers-tvx !

Only granting to (and revoking from) Redshift users was explicitly covered in the original implementation of grants in #131 -- granting/revoking for Redshift groups and roles was not.

This deserves clarification in the docs, and I've opened dbt-labs/docs.getdbt.com#3245 accordingly.

I'm going to convert this into a feature request to add support for grants for Redshift groups and roles.

[amardatar]

We use this extensively, and intentional or not it seems that just using group <group_name> works perfectly fine. @stevenayers-tvx does it work if you just do this?

models:
  - name: specific_model
    config:
      grants:
        select: ['group finance_department']

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[joellabes]

Reopening as the PR that relates to it is still open