You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is a proper separation between cmd and logic in planning? This would allow developers to use ignite as sdk.
For example:
If you want to execute a command programmatically in the container (because entrypoints are unfortunately not supported) a method runSSH is executed in which defer os.Exit is called, which is of course impractical :D
Another example would be the creation of vm's. There is a method that takes []string args and a FlagSet and directly builds a vm. A separation between the cmd and run package would be very useful.
I think this project is only used in projects where untrusted user code is executed in a sandbox. A SDK would make a lot of sense here, since this type of vm's are created programmatically anyway.
Unfortunately there is not so much active work on this project although I think it has a lot of potential!
Is a proper separation between cmd and logic in planning? This would allow developers to use ignite as sdk.
For example:
If you want to execute a command programmatically in the container (because entrypoints are unfortunately not supported) a method
runSSHis executed in whichdefer os.Exitis called, which is of course impractical :DAnother example would be the creation of vm's. There is a method that takes []string args and a FlagSet and directly builds a vm. A separation between the cmd and run package would be very useful.
I think this project is only used in projects where untrusted user code is executed in a sandbox. A SDK would make a lot of sense here, since this type of vm's are created programmatically anyway.
Unfortunately there is not so much active work on this project although I think it has a lot of potential!