Able to create a new job

[martinraynov]

Reason/Context

To be able to create a new job import from specifications available on other servers

Description

I am using a lot of specifications available on github enterprise servers.
With the microcks UI I can add them with the Importers -> Create a new Job feature but in the cli I can only import files that are located on the machine that executes the command.

Implementation ideas

Maybe the microcks-cli import function can be extended to accept also URLs

[github-actions]

👋 @martinraynov

Welcome to the Microcks community! 💖

Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

Hope you have a great time there!

🌟 ~~~~~~~~~ 🌟

📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

[lbroudoux]

Thanks for the suggestion @martinraynov !

Actually, the CLI needs to be refactored a bit and we started a 1.x branch a long time ago (see https://github.com/microcks/microcks-cli/tree/1.x). to start this effort. The idea would be to integrate some classic CLI tools libraries like Viper and others to have something extensible in the long term.

Some contributors have already started the effort (like @JulienBreux - see https://github.com/JulienBreux/mksctl) but we need more cycles to get this running and integrate new commands.

So it's a big YES for this feature but I think it would be better to pursue on refactoring first.

[cstv4]

Hey @lbroudoux @Harsh4902, is this issue resolved by #98 or something more needs to be done?. Thank you

[Harsh4902]

@cstv4 Yes, it's resolved now.

[Harsh4902]

@martinraynov As this issue has already been resolved by #98, can we close it?
CC: @lbroudoux