heroku / heroku/roadmap

Deploy permissions should not give access to addons

Open
#105 6 comments 27 reactions 0 assignees View on GitHub
Proposed Security
Dominant language
No language data
Stars
225
Forks
19
PR merge metrics
No merged PRs in 30d

Description

### Required Terms

- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)

### What service(s) is this request for?

Security, Postgres, Addons

### Tell us about what you're trying to solve. What challenges are you facing?

```markdown
There is a major security issue with deploy permissions and addons. The best example is PostgreSQL addons.

If you give a user deploy access then they get full access to the addon. They are able to connect to the database with full read/write permissions.

We should be able to give a user deploy permissions but restrict access to sensitive addons like private databases.
```

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.