I went with two variables because we often overrides helm variables and setting a value to false in a chart is easier than removing it completely.
I added functions to wait that the workspace is uploaded, variables too and a new run is needed and then start a new run. I have little to no experience in kubernetes operator development so it may be the wrong logic here.
Usage Example
spec:
initialRun: true
initialRunType: apply
Will queue an apply run when the workspace is created and all the variables are uploaded
References
Fixes: GH-212
Community Note
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
This pr adds the ability to queue an initial run at the workspace creation It adds two fields:
I went with two variables because we often overrides helm variables and setting a value to false in a chart is easier than removing it completely.
I added functions to wait that the workspace is uploaded, variables too and a new run is needed and then start a new run. I have little to no experience in kubernetes operator development so it may be the wrong logic here.
Usage Example
Will queue an apply run when the workspace is created and all the variables are uploaded
References
Community Note