-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: database role resource #1654
Conversation
pkg/resources/database_role.go
Outdated
row := snowflake.QueryRow(db, qry) | ||
// FIXME scan for name as there is LIKE pattern syntax | ||
databaseRole, err := snowflake.ScanDatabaseRole(row) | ||
databaseRole.DatabaseName = database // Nasty. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not understanding what the point of this is. If database name is a ForceNew attribute then theres no reason to read or overwrite it at all since its never going to change.
) | ||
|
||
type ( | ||
TestAccDatabaseRoleSettings struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this is a bit overkill. probably better to just have a function like databaseRoleConfig(warehouseName, databaseName, roleName
)
@mlorek this is interesting an highlights a deficiency in the currently provider. we will also need to a |
added database role resource: #1442
Test Plan
References
https://docs.snowflake.com/en/user-guide/security-access-control-considerations#label-access-control-considerations-database-roles
*