> + > +import static org.jclouds.reflect.Reflection2.typeToken; > +import java.net.URI; > +import java.util.Properties; > + > +import org.jclouds.apis.ApiMetadata; > +import org.jclouds.blobstore.BlobStoreContext; > +import org.jclouds.labs.b2.config.B2HttpApiModule; > +import org.jclouds.rest.internal.BaseHttpApiMetadata; > + > +import com.google.auto.service.AutoService; > +import com.google.common.collect.ImmutableSet; > +import com.google.inject.Module; > + > +@AutoService(ApiMetadata.class) > +// TODO: B2ProviderMetadata?
Yes. The api metadata should just describe the API, and the provider metadata should add to the API the real endpoint (apis can provide a default one), and the default configuration. For providers that have their own API this makes less sense, but I think it is still good to separate both. HAve a look at the digitalocean2 provider for an example. You may also want to use the same provider id for the api and provider, so just remove this annotation once the provider metadata exists, to avoid having conflicts. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/270/files/08f67d68c03760ce134ccf217c3b1ee4487ac318#r64119825
