Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide more context to Snowflake Permissions page #3824

Closed
1 task done
mirnawong1 opened this issue Jul 27, 2023 · 1 comment · Fixed by #3943
Closed
1 task done

Provide more context to Snowflake Permissions page #3824

mirnawong1 opened this issue Jul 27, 2023 · 1 comment · Fixed by #3943
Assignees
@matthewshaver @mirnawong1
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows size: small This change will take 1 to 2 days to address

Comments

@mirnawong1
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

Per slack thread, the Snowflake permissions page has no context or info around it.

Discourse page has more info around this than the docs, which seems reverse.

We should add contextual info, as a minimum, on this page.

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/reference/snowflake-permissions

Additional information

No response
@mirnawong1 mirnawong1 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Jul 27, 2023
@runleonarun runleonarun added size: small This change will take 1 to 2 days to address priority: medium Fix or enhancement to existing information that’s creating some requests from customers labels Jul 27, 2023
@runleonarun
Copy link
Collaborator

Here's the original PR that added the permission page.

@runleonarun runleonarun added priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows and removed priority: medium Fix or enhancement to existing information that’s creating some requests from customers labels Jul 27, 2023
@runleonarun runleonarun mentioned this issue Aug 22, 2023
Closed
1 task
@mirnawong1 mirnawong1 self-assigned this Nov 1, 2023
mirnawong1 added a commit to agnessnowplow/docs.getdbt.com that referenced this issue Nov 1, 2023
@mirnawong1
Update snowflake-permissions.md
03ddf3e 
adding discourse article to resolves issue dbt-labs#3824
@mirnawong1 mirnawong1 mentioned this issue Nov 1, 2023
Merged
6 tasks
mirnawong1 added a commit that referenced this issue Nov 1, 2023
@mirnawong1
Add more warehouses to database permissions (#3943)
5422e9a 
## What are you changing in this pull request and why?
The proposed changes are regarding this issue raised last week:
#3901

It would be nice to have more warehouses within References / warehouse
permissions with sample grants, this PR aims to follow the already
existing
[Snowflake](https://docs.getdbt.com/reference/snowflake-permissions)
example and add Databricks, Redshift, and Postgres as well (skipping
BigQuery due to their unique IAM access control management)

#Resolves #3824

## Checklist
<!--
Uncomment if you're publishing docs for a prerelease version of dbt
(delete if not applicable):
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
-->
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [x] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):
- [x] Add page to `website/sidebars.js`
- [x] Provide a unique filename for the new page

- [x] Needs to have a technical review, at least to verify the proposed
changes are correct and possibly expand with other examples.
- [x] Tested it locally (npm run)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matthewshaver matthewshaver

@mirnawong1 mirnawong1

Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows size: small This change will take 1 to 2 days to address
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add more warehouses to database permissions agnessnowplow/docs.getdbt.com
3 participants
@runleonarun @matthewshaver @mirnawong1