puter/paseo
1
0
Fork 0
mirror of https://github.com/getpaseo/paseo.git synced 2026-10-24 18:22:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(hub): clarify credential storage and retention

Browse Source
This commit is contained in:
Mohamed Boudra
2026-09-10 08:21:13 +02:00
parent c56c4bb390
commit 757bf81cb9
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
public-docs/hub/github.md
+5 -1
View File
@@ -79,4 +79,8 @@ env:
SOME_TOKEN: "${{ paseo.connections.some-connection.token }}"
```
Hub persists resolved values as private execution data so it can recover after a restart. Authored configuration retains the expressions. See [Hub security](/docs/hub/security) for provider and host boundaries.
Hub persists resolved values as private execution data so it can recover after a restart. Authored configuration retains the expressions.
These values are stored in the Hub database without application-level encryption. Protect database access, storage, and backups as credentials. Hub deletes the execution authority record when the execution becomes terminal; token lease records remain until revocation succeeds or the token expires, so interrupted cleanup can resume. This cleanup is not a guarantee that every copy is erased: retained agent/session data and database backups may still contain resolved values. Token revocation ends access; it does not erase those copies. Backup retention and deletion remain the operator’s responsibility.
See [Hub security](/docs/hub/security) for provider and host boundaries.