Skip to content

Commit 779726f

Browse files
author
Christopher Giroir
committed
doc: secret manager improvements
1 parent 5fe4ddb commit 779726f

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

docs/cloud/features/scheduler/scheduler.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -169,10 +169,17 @@ SQLMesh automatically infers which Python libraries are used by statically analy
169169

170170
For fine-grained control, dependencies can be specified, pinned, or excluded using the `sqlmesh-requirements.lock` file. See the [Python library dependencies](../../../guides/configuration.md#python-library-dependencies) section in the SQLMesh configuration guide for more information.
171171

172-
## Secrets
172+
## Secret Manager
173173

174174
Tobiko Cloud provides a way for you to provide environment variables that will
175-
be injected into the environment when running your python models.
175+
be injected into the environment when running your python models. The values
176+
of these variables are encrypted at rest and only available in the environment
177+
of your running models.
178+
179+
!!! note "Cloud Scheduler Only"
180+
181+
Secrets from the secret manager do not load into hybrid executors. They are
182+
only used for cloud scheduler executors.
176183

177184
In your cloud instance you can find Secrets under the Settings section and will
178185
look like this:
@@ -188,7 +195,7 @@ letters, numbers and underscores (no spaces or other symbols). There are no
188195
limits or restrictions on the value of secrets. We recommend base64 encoding
189196
secrets if they contain binary data.
190197

191-
### Example Secret Use
198+
### Python Model Example
192199

193200
```python
194201
import os

0 commit comments

Comments
 (0)