Add missing docs
For the pre_render_scripts feature
- [Readiness and Liveness Probes](#Readiness-and-Liveness-Probes)
- [Persistent Disks](#Persistent-Disks)
- [Manual ("implicit") variables](#Manual-%22implicit%22-variables)
+ - [Pre_render_scripts](#Pre_render_scripts)
- [Flow](#Flow)
- [Naming Conventions](#Naming-Conventions)
@@ -541,6 +542,37 @@ stringData:
value: example.com
```
+### Pre_render_scripts
+
+Similar to what can be achieved in SCF v1, with the [patches](https://github.com/SUSE/scf/tree/develop/container-host-files/etc/scf/config/scripts/patches) scripts, the `cf-operator` is able to support this behaviour. Basically, it allows the user to execute a custom script during runtime of the job container for a specific `instance_group`. Because patching during runtime is always a great feature to have, for a variety of reasons, users can specify this via the `quarks.pre_render_scripts` key.
+
+Keep it mind, that the script should belong to a type, to avoid running all scripts as a whole. Currently supported types are:
+
+- `quarks.pre_render_scripts.bpm`.
+- `quarks.pre_render_scripts.ig_resolver`
+- `quarks.pre_render_scripts.jobs`
+
+This allows you to run anything, by specifying a list of commands/scripts to execute. For example:
+
+```sh
+instance_groups:
+- name: redis-slave
+ instances: 2
+ lifecycle: errand
+ azs: [z1, z2]
+ jobs:
+ - name: redis-server
+ release: redis
+ properties:
+ quarks:
+ pre_render_scripts:
+ bpm:
+ - |
+ touch /tmp
+
+```
+
+
## Flow
![flow](https://docs.google.com/drawings/d/e/2PACX-1vSsapirEQTlBvFDYjRbCxK5IJaxRqPDfTi37OcBVr60BGbDThn83HeHJyRModicUeghc7enfyYY_CHI/pub?w=1279&h=997)
