> + public AzureComputeProviderMetadata(final Builder builder) {
> + super(builder);
> + }
> +
> + public static class Builder extends BaseProviderMetadata.Builder {
> +
> + protected Builder() {
> + super();
> +
> + id("azurecompute-arm")
> + .name("Azure Resource Management ")
> + .apiMetadata(new AzureManagementApiMetadata())
> +
> .endpoint("https://management.azure.com/subscriptions/SUBSCRIPTION_ID";)
> + .homepage(URI.create("https://www.windowsazure.com/";))
> +
> .console(URI.create("https://windows.azure.com/default.aspx";))
> + .linkedServices("azureblob", "azurequeue", "azuretable")
Sure, this refers to provider ids of provieders existing in jclouds. For
example, in AWS EC2, we have linked services such as "aws-elb" (AWS Elastic
Load Balancers), "aws-elb", "aws-cloudwatch" or "aws-s3", which are all
existing jclouds providers a user can instantiate using the ContextBuilder and
the same credentials.
In this case, the only provider available in jclouds is "azureblob", so I'd
leave just that one.
---
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/250/files/8d7d68bf33361d7f5df68c7e7232b03116ed6977#r58624811
