search

pry0cc / axiom

The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
MIT License
4k stars 622 forks source link

axiom warning output using linode-cli #616

Closed bart3nder closed 2 years ago

bart3nder commented 2 years ago

Hi! Thanks for amazing project, really useful. So I get an error whenever axiom is interacting with linode-cli (axiom-fleet, axiom-ls, axiom-rm ...) saying:

Unable to determine if a new linode-cli package is available in pypi.  If this message persists, open a ticket or invoke with --suppress-warnings

It's still functioning correctly but it is some how slower due showing the error every single time. Is there anyway that I can fix it? I tried pip3 uninstall linode-cli and pip3 install linode-cli but no luck. Thank you!

pdelteil commented 2 years ago

Maybe (as a temporary solution) you could create an alias:

linode-cli='linode-cli --suppress-warnings'

I'm not sure it would work.

bart3nder commented 2 years ago

Hmm, didn't think that way. I just checked and unfortunately it didn't worked. Thanks for your time Philippe!

pdelteil commented 2 years ago

I think the alias should be created on every instance, not on the local machine.

bart3nder commented 2 years ago

Hello again! Sorry for late response, Can you please explain more how can I do that? I didn't fully understand.

pdelteil commented 2 years ago

No problem. You want to get rid of the warning message, in order to do that without reinstalling linode-cli you could set up an alias linode-cli='linode-cli --suppress-warnings', that way every instance of your axiom fleet will run the command linode-cli but without the warnings, it's a trick.

To do this you will need to add the alias to the .bashrc file of every instance. Something like this:

axiom-exec 'echo "alias linode-cli=\"linode-cli --suppress-warnings\"" >> .bashrc'

I don't think is necessary but just in case run:

axiom-exec 'source /home/op/.bashrc'

Now try running axiom again.

bart3nder commented 2 years ago

Ah, so it's like that, huh. I thought you meant I have to edit the axiom setup source to reach that. I understand that now. I did what you said but apparently there is no CLI tool for cloud providers (or at least for linode) on created instances, so the alias solution won't work since the only machine who is responsible to interact with the API is the local one and alias thing didn't fixed it (Still don't know why, I can not see any error or ...) Thank you again for your time Philippe, I think I should go for deep uninstalling to fix the problem.

pdelteil commented 2 years ago

You are correct. I was wrong!

But still the same should work on your local machine. I'll try on my instalation later.

On Sat, Sep 17, 2022, 02:50 deBartender @.***> wrote:

Ah, so it's like that, huh. I thought you meant I have to edit the axiom setup source to reach that. I understand that now. I did what you said but apparently there is no CLI tool for cloud providers (or at least for linode) on created instances, so the alias solution won't work since the only machine who is responsible to interact with the API is the local one and alias thing didn't fixed it (Still don't know why, I can not see any error or ...) Thank you again for your time Philippe, I think I should go for deep uninstalling to fix the problem.

— Reply to this email directly, view it on GitHub https://github.com/pry0cc/axiom/issues/616#issuecomment-1250023350, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2OS7332LG4BRH4OWJAVJDV6VZ4TANCNFSM6AAAAAAQNKXBVA . You are receiving this because you commented.Message ID: @.***>

bart3nder commented 2 years ago

Instead of alias linode-cli='linode-cli --suppress-warnings', I edited ~/.axiom/providers/linode-functions.sh directly and replaced every linode-cli with linode-cli --suppress-warnings. I can confirm it is fixed and works without any problem now. Thank you!

pdelteil commented 2 years ago

Yes, that was the boring solution 😂 😂 😂 😂

On Sat, Sep 17, 2022, 15:31 deBartender @.***> wrote:

Instead of alias linode-cli='linode-cli --suppress-warnings', I edited ~/.axiom/providers/linode-functions.sh directly and replaced every linode-cli with linode-cli --suppress-warnings. I can confirm it is fixed and works without any problem now. Thank you!

— Reply to this email directly, view it on GitHub https://github.com/pry0cc/axiom/issues/616#issuecomment-1250136228, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2OS75KHXC77E7PKTN2U2TV6YTCDANCNFSM6AAAAAAQNKXBVA . You are receiving this because you commented.Message ID: @.***>