[ADAP-1086] [Bug] Grants are failing during incremental runs when data shares are present on serverless

[mikealfare]

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

Users are running into production failures with incremental models. It looks like this is failing due to Redshift listing consumer cluster users for data shares in system tables/views. dbt is using those tables/views to generate revoke statements and they fail on those remote users.

Expected Behavior

Grants should be properly handled during incremental runs.

Steps To Reproduce

project.yml

models:
  teal_business_vault:
    materialized: table
  +grants:
    select: ['group dbt_developers']
    all: ['group etl_powerusers']

Relevant log output

The issue is errors being returned:

SQL Error [0A000]: ERROR: Granting permissions to reserved user <redacted> is not supported." when running with incremental logic. (edited)

Example failed run: https://emea.dbt.com/deploy/161/projects/1466/runs/2879012

Environment

- OS: linux
- Python: 3.8
- dbt-core: 1.6.9
- dbt-redshift: 1.6.5

Additional Context

ZenDesk: https://dbtcloud.zendesk.com/agent/tickets/59389
Potentially related: #626

[mike-wilson-tubi]

We are experiencing this issue as well. We have a provisioned Redshift cluster with a datashare to a Serverless Redshift cluster. We are receiving the error:

2024-01-09 19:28:10.273561 (Thread-2): 19:28:10  Redshift adapter: Redshift error: Granting permissions to reserved user ds:reporting_acc_111305045888 is not supported.

We have confirmed with AWS that this user is related to consumer Serverless account that is created in the Provisioned cluster. This is a "reserved" user per the error message and grants and revokes on the user will fail with the above error message.

[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.