This logic for assuming that a url is internal based off of the start of the url string is not correct. For instance at my company we have urls defined like so:
Where we have a use case where we are connecting to our internal sonar from our internal jenkins instance, and we expect to be able to provide a SONAR_TOKEN to do so. There is no issue using the general purpose sonar-scanner for this use case. However when we use the sonar/scan npm dependency we run into issues with the above mentioned code.
We would prefer a bugfix for this to enable our use case; as the Sonar NPM package provides useful capturing of package details automatically.
what is the problem you are facing exactly when using those URLs? Can you please share what is the full command line you are using and what is your expected behaviour vs what is actually happening? internal vs external is mostly to know if we are facing a sonar instance or not.