Commit eac3065
committed
feat: censor sensitive fields in API responses
With this change, the following sensitive fields will be omitted from
all API responses:
- Database user passwords
- Backup and restore repository credentials:
- S3 keys/secrets
- Azure keys
- GCS keys
We want to enable users to manage databases without storing the original
create request. So, this commit also changes the update behavior so that
these sensitive fields can be omitted from update requests. This makes
it safe to store the database spec in version control.
Users can modify the credentials, such as when rotating passwords, by
including the updated values in an update request.
PLAT-861 parent 1293ea0 commit eac3065
File tree
17 files changed
+777
-131
lines changed- api/v1
- design
- gen
- control_plane
- views
- http
- control_plane
- client
- server
- changes/unreleased
- server/internal
- api/v1
- database
- pgbackrest
- utils
17 files changed
+777
-131
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
80 | 80 | | |
81 | 81 | | |
82 | 82 | | |
83 | | - | |
| 83 | + | |
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
| |||
101 | 101 | | |
102 | 102 | | |
103 | 103 | | |
104 | | - | |
| 104 | + | |
105 | 105 | | |
106 | 106 | | |
107 | 107 | | |
| |||
134 | 134 | | |
135 | 135 | | |
136 | 136 | | |
137 | | - | |
| 137 | + | |
138 | 138 | | |
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
142 | 142 | | |
143 | | - | |
| 143 | + | |
144 | 144 | | |
145 | 145 | | |
146 | 146 | | |
| |||
157 | 157 | | |
158 | 158 | | |
159 | 159 | | |
160 | | - | |
| 160 | + | |
161 | 161 | | |
162 | 162 | | |
163 | 163 | | |
| |||
180 | 180 | | |
181 | 181 | | |
182 | 182 | | |
183 | | - | |
| 183 | + | |
184 | 184 | | |
185 | 185 | | |
186 | 186 | | |
| |||
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments