Skip to content

Documented existing requirement for SQL privileges #367

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

Merged
merged 1 commit into from
Jun 21, 2024
Merged

Documented existing requirement for SQL privileges #367

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,9 @@ It is important for the namespace temp folder to be owned by the user IRIS runs
If you want to interact with remotes from VSCode/Studio directly (e.g., to push/pull), you must use ssh (rather than https), create a public/private key pair to identify the instance (not yourself), configure the private key file for use in Settings, and configure the public key as a deploy key in the remote(s).

#### IRIS Privileges
For developers to be able to run this extension, they'll need the USE privilege on %System_Callout.
For developers to be able to run this extension, they'll need the following privileges:
- the USE privilege on %System_Callout
- SQL SELECT privileges on %Studio_SourceControl.Change and SourceControl_Git.Change

### Setting up multiple GitHub deploy keys on one machine

Expand Down
Loading