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
Hi, in the following PR #3007 was introduced support of hosted repositories, but as a result, dart client throws an exception when you're trying to add a token for repository with HTTP protocol:
url must be https://, insecure repositories cannot use authentication.
We're working on support of Dart packages hosting as part of our product and would like to run integration tests by using the current dart client against local service (HTTP) in CI environment. Currently, it's impossible to opt-out from that security verification check.
What we could do with that:
Introduce the ability to disable security check as it is done in other tools, e.g. skopeo --tls-verify=false.
Fork the client and make our own builds without HTTPS enforcement.
The first option is preferred for us, but what is the Dart team opinion about that?
The text was updated successfully, but these errors were encountered:
You can look into ngrok (https://ngrok.com/)
Or you can create custom token files (they are not checked at usage).
If these are not sufficient for your purposes we might accept a contribution that allows insecure hosts only if they are localhost (but with not command-line option).
Hi, in the following PR #3007 was introduced support of hosted repositories, but as a result,
dart
client throws an exception when you're trying to add a token for repository with HTTP protocol:Reference:
pub/lib/src/command/token_add.dart
Line 47 in efd24e6
We're working on support of Dart packages hosting as part of our product and would like to run integration tests by using the current
dart
client against local service (HTTP) in CI environment. Currently, it's impossible to opt-out from that security verification check.What we could do with that:
skopeo --tls-verify=false
.The first option is preferred for us, but what is the Dart team opinion about that?
The text was updated successfully, but these errors were encountered: