Summary
Propose adding support for user-provided custom templates as input to the Holodeck config file. This allows users to specify custom scripts to be executed during the provisioning stage, enabling further customization of the target host setup.
Motivation
Currently, Holodeck only uses built-in provisioning templates. By allowing users to provide their own templates/scripts, it adds flexibility for advanced users who need to run additional setup steps.
Proposed Behavior
- Users can specify one or more custom templates/scripts in the Holodeck config file.
- During provisioning, Holodeck will execute its built-in templates first.
- After all built-in templates have run, it will execute the user-provided custom script(s).
- This allows users to configure the target host with any additional tools, dependencies, or settings as needed.
Benefits
- Greater flexibility for users to customize the provisioning process.
- Supports advanced use-cases without modifying Holodeck core.
Example Use Cases
- Installing additional system packages
- Configuring environment variables
- Running custom initialization logic
Implementation Notes
- Ensure that custom scripts are executed after all Holodeck defaults.
- Validate and sanitize user input for security.
This feature would enhance Holodeck's extensibility and user control over the provisioning process.
Summary
Propose adding support for user-provided custom templates as input to the Holodeck config file. This allows users to specify custom scripts to be executed during the provisioning stage, enabling further customization of the target host setup.
Motivation
Currently, Holodeck only uses built-in provisioning templates. By allowing users to provide their own templates/scripts, it adds flexibility for advanced users who need to run additional setup steps.
Proposed Behavior
Benefits
Example Use Cases
Implementation Notes
This feature would enhance Holodeck's extensibility and user control over the provisioning process.