tuftool's native-tls/rustls switch doesn't affect reqwest

[iliana]

We have:

tough/tuftool/Cargo.toml

Lines 11 to 15 in 9ac95c8

	[features]
	default = ["rusoto"]
	rusoto = ["rusoto-rustls"]
	rusoto-native-tls = ["rusoto_core/native-tls", "rusoto_credential", "rusoto_ssm/native-tls"]
	rusoto-rustls = ["rusoto_core/rustls", "rusoto_credential", "rusoto_ssm/rustls"]

but we also depend on reqwest, and we aren't switching which TLS implementation it uses.

Ideally I'd like to be able to enable/disable rusoto_ssm and switch between native-tls and rustls separately but I don't know if that's possible.

[webern]

I opened this, which seems related: #271

[webern]

Actually... does tuftool need to give the user this configurability? Since it is a command-line tool and will always be compiled in isolation, what is the benefit of giving a user the ability to choose native-tls (assuming we chose rustls)?

[iliana]

Honestly I'd go the other direction and use native-tls in tuftool, if we're going to make the choice for the user.

[webern]

Moving this out of the v0.10.0 milestone as the v0.10.0 diff is already huge and releasing it sooner rather than later moves things in the right direction.