Detect specific supported cloud providers about cloud-detect

[kshivakumar]

@dwc0011

...trying to detect the others is a waste of time and resources

There's no waste of time since all the providers are checked concurrently. When the correct provider is identifier, other checks are cancelled immediately.
I don't think any application that uses this library will check the cloud provider every other minute or hour, making few additional http requests once in a while is not waste of resources.
Moreover, by not having to pass my_providers to the provider function we keep our api simple.

The only case where the library takes considerable time to respond is when the environment is not one of the supported cloud providers. See this comment for additional info - #12 (comment).
When the environment is supported, the response is almost instantaneous.

[dwc0011]

@kshivakumar

Moreover, by not having to pass my_providers to the provider function we keep our api simple.

I understand that you wish to keep the api simple, but at the same time I understand the need for not checking for resources that will never be. An optional param is also still pretty simple to me, heck this feature was even part of the API up until April, just as an opposite "excluded" param.

The only case where the library takes considerable time to respond is when the environment is not one of the supported cloud providers.

This is the exact case I am trying to prevent, we wanted to use in our application which does run quite often on environments that are not supported. The more cloud providers it has to check the more resources and time that is wasted, even if concurrent.

I appreciate you responding and hope that you reconsider but I understand either way. Feel free to close if your decision is final. Thanks.