-
Notifications
You must be signed in to change notification settings - Fork 22
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
Use mesheryctl
not bash
#20
Comments
// @navendu-pottekkat @piyushsingariya @DelusionalOptimist @s1ntaxe770r @hexxdump |
I'll take this one |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unassigning to free up issue for another contributor to pick up. @s1ntaxe770r please self-assign if you end up coming back t o this. |
Oh @leecalcote i opened a PR, it's still in review |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Current Behavior
Current tests use bash scripts to deploy service meshes and apps, but should be using
mesheryctl mesh
andmesheryctl app
.Contributor Guide
The text was updated successfully, but these errors were encountered: