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

subctl should be refactored to a library, and make subctl the CLI of that library #1329

Closed
48 tasks done
mangelajo opened this issue May 4, 2021 · 4 comments · Fixed by #1651, #1735, #1717, #1770 or #1980
Closed
48 tasks done

Comments

@mangelajo
Copy link
Contributor

mangelajo commented May 4, 2021

What would you like to be added:

Splitting subctl in two parts, an interface part, and a library part, the library would contain all the logic
that subctl uses, and a defined Interface that external projects can consume

Why is this needed:

In this way, other projects can use the subctl logic to deploy clusters and brokers in an automated
way without calling the subctl logic from the command line.

Work items:

Just few examples. Follow
https://github.com/golang-standards/project-layout
https://medium.com/golang-learn/go-project-layout-e5213cdcfaa2
https://vsoch.github.io/2019/go/

@mangelajo mangelajo added the enhancement New feature or request label May 4, 2021
@mangelajo
Copy link
Contributor Author

@mkolesnik ping ^

@mkolesnik
Copy link
Contributor

/cc @skeeey @zhiweiyin318 @qiujian16 would this be useful for your ACM plugin?

@mangelajo
Copy link
Contributor Author

This would also be beneficial for testing because we could test subctl better by having good interfaces that we can mock.

@github-actions
Copy link

This PR/issue depends on:

@Jaanki Jaanki closed this as completed May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment