Open mharwani opened 1 year ago
Similar to https://github.com/runfinch/finch/issues/237#issuecomment-1442443536, to provide a seamless VM experience that the users don't feel VM is existing, we can think about the alternative approach, making the "custom scripts" Finch extensions.
What is the problem you're trying to solve?. As a developer, I'd like to customize the VM with my own scripts during initialization so that I can install additional packages, fix VM related issues, or apply configurations for my specific needs. For example, I can use a custom provisioning script to install credential helpers for a better login experience with ECR and other container registries.
Describe the feature you'd like I'd like Finch to execute all provisioning scripts in a directory (eg:
~/.finch/provisioning
) during VM initialization or start. These scripts should be executed inside the VM. Finch should also notify users if the script failed and display error messages if any.Additional context This is a nice to have feature that can help certain developers customize the VM to fit their specific needs and use cases. Currently, if developers want to make any changes to the guest system, they have to shell into the VM and the changes are not persisted after the VM instance is removed or Finch is updated to a newer version.