Skip to content
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

Internalize zarf tools wait-for #104

Open
Racer159 opened this issue May 28, 2024 · 1 comment
Open

Internalize zarf tools wait-for #104

Racer159 opened this issue May 28, 2024 · 1 comment
Labels
enhancement ✨ New feature or request

Comments

@Racer159
Copy link
Contributor

Is your feature request related to a problem? Please describe

We should internalize the logic of the wait actions to that it no longer needs to shell out to Zarf.

Describe the solution you'd like

  • Given I do not have Zarf on my path
  • When I run a Maru task containing a wait action (either cluster or network)
  • Then the wait action finishes successfully

Describe alternatives you've considered

We could not do this, or introduce another key to place this logic under but it should be relatively easy to match the current wait syntax while maintaining functionality.

Additional context

There is already a PR for some of this in Zarf: https://github.com/defenseunicorns/zarf/pull/2497/files

@Racer159 Racer159 added the enhancement ✨ New feature or request label May 28, 2024
@marshall007
Copy link

Related to #102 which I plan to knockout first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants