Conversation
|
| Filename | Overview |
|---|---|
| docs/use-cases/preview-environments.md | Adds accurate preview mount guidance and examples, but the new full-config-reference link points to a nonexistent path. |
Reviews (1): Last reviewed commit: "small edit" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| Files are read once at session creation and never refreshed. Re-run `mirrord preview start` with the same key to pick up changes. | ||
| {% endhint %} | ||
|
|
||
| Combined payload size across all mounts in a session is bound by Kubernetes' ~1 MiB per-object limit. See the [full config reference](../config/options md#feature-preview-config_mounts) for the complete field list. |
There was a problem hiding this comment.
The new ../config/options md#feature-preview-config_mounts target contains a space and points to a page that does not exist in the documentation tree, so readers cannot reach the promised configuration reference.
| Combined payload size across all mounts in a session is bound by Kubernetes' ~1 MiB per-object limit. See the [full config reference](../config/options md#feature-preview-config_mounts) for the complete field list. | |
| Combined payload size across all mounts in a session is bound by Kubernetes' ~1 MiB per-object limit. See the [full config reference](https://metalbear.com/mirrord/docs/config/options#feature-preview-config_mounts) for the complete field list. |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
|
||
| ### Overriding Config and Secret Files | ||
|
|
||
| Testing a config change usually means rebuilding and pushing a new image just to change one file. `config_mounts` and `secret_mounts` override or inject individual files into the preview pod without touching the image, by adding them to the same mirrord configuration file used to start the preview. |
There was a problem hiding this comment.
Nope. You use config mounts/secret mounts to override the spec/yaml, not the image. You might be able to override image things but that's not hte main use case.
"If you'd like to test your image with a change to the configmap or secrets, you can use the.."
2 participants
No description provided.