-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Powershell Task #2
Comments
I'm assuming we expect the powershell scripts to be stored in the same catalog as the devboxyaml, hence a different catalog than our sample task repo |
@xnkevinnguyen @DavidObando the one caveat here is: do we really need to specify a "RunDuring" here, if we could just have a higher level devbox.yaml construct? |
this can be an escape hatch command. While we wait for customer feedback on how to structure a devbox.yaml in a way to infer when something ought to run Notes from v-team meeting: when you attach catalog and press sync - we search for devboxyaml and task yaml. these files are ingested. for each task, we cache the folder where we found the said task. (these go to storage account). feedback:
|
Ok, then we can go ahead and start with the solution mentioned above. |
Run a linked powershell script as a Dev Box customization task
Describe the solution you'd like
As a user, I should be able to:
Sample usage:
The text was updated successfully, but these errors were encountered: