-
Notifications
You must be signed in to change notification settings - Fork 100
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
Move InvokeGenerator to a centralized function of Meshkit. #541
Comments
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack. |
@Jougan-0 We should reassign this issue. |
I think Aviral could do it. Thoughts? |
I'll complete this PR after adding some recent changes |
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. |
Current Behavior
When we run
mesheryctl registry generate
we InvokeGenerator directly inside the mesheryctl command rather it should be a centralized function in meshkit that can be reused in server as well.Desired Behavior
Update meshkit to contain this functionality.
Resources
Alternatives / Additional Context
The text was updated successfully, but these errors were encountered: