dazzling-scientist-80826
08/12/2018, 8:48 PMaverage-wire-57068
08/12/2018, 9:07 PMconst bucket = new aws.s3.Bucket("my-bucket", {
acl: "public-read"
});
the result was a bucket named: my-bucket-e48aec4
The following code:
const storage = new azure.storage.Account("divgopulumi", {
location: 'eastus',
resourceGroupName: 'MyRG',
accountReplicationType: "LRS",
accountKind: "StorageV2",
accessTier: "Cool",
accountTier: "Standard",
customDomain: {
name: "<http://files.mydomain.com|files.mydomain.com>",
useSubdomain: true
}
})
resulted in a storageAccount named: divgopulumic91925bb
My question is: how do I generate these objects without the trailing random characters?big-piano-35669
const bucket = new aws.s3.Bucket("my-bucket", {
bucket: "my-bucket",
... as before ...
});
and
const storage = new azure.storage.Account("divgopulumi", {
name: "divgopulumi",
...
});
Most of the time, the property is called name
, however unfortunately the S3 Bucket type is the odd duck here, with bucket
.
We've been discussing what to do here, such as a global flag like --no-auto-names
as we know not everybody wants the name mangling, and it can be tedious to override this on every single resource. Also, Azure isn't as bad as AWS, since names only need to be unique within a ResourceGroup.
Feedback definitely appreciated on the topic.average-wire-57068
08/12/2018, 9:21 PMbest-tent-29186
08/13/2018, 8:32 AMgray-city-50684
08/13/2018, 12:38 PMgray-city-50684
08/13/2018, 12:39 PMwhite-balloon-205
~/.pulumi/workspaces
. You can update the active stack with pulumi stack select
.gray-city-50684
08/13/2018, 1:07 PMgray-city-50684
08/13/2018, 1:09 PMgray-city-50684
08/13/2018, 1:10 PMwhite-balloon-205
0.15.0
release which we expect to release today (currently 0.15.0-rc2
is published and being tested).
On 1. this was added with https://github.com/pulumi/pulumi-azure/pull/86. I haven't used this yet myself, but the two Terraform Azure Provider resources you note are now available in Pulumi.
On 2. we've added support for "1st class providers" in 0.15.0
which allows you to do new kubernetes.Provider({ kubeconfig: ..., context: ... })
to create a new Kubernetes provider configured with a kubeconfig that was potentially computed as a result of other operations. We'll have an example of this exact use case (AKS + Kubernetes deployments) published along with the release later today. You can see a simple example here: https://github.com/pulumi/pulumi-kubernetes/blob/a2ba053df34ecb980c8d218a47f6208cd7e7282f/examples/provider/index.tsgray-city-50684
08/13/2018, 1:22 PMbland-lamp-97030
08/13/2018, 1:25 PMfatal: [500] Internal Server Error
bland-lamp-97030
08/13/2018, 1:25 PMhelpful-vegetable-35581
08/13/2018, 4:11 PMchilly-crayon-57653
helpful-vegetable-35581
08/13/2018, 4:33 PMcolossal-beach-47527
08/13/2018, 5:07 PMadventurous-jordan-10043
08/13/2018, 8:37 PMadventurous-jordan-10043
08/13/2018, 8:38 PMhelpful-vegetable-35581
08/14/2018, 11:15 AMstocky-spoon-28903
08/14/2018, 1:18 PMprod-
or whatever)white-balloon-205
adamant-restaurant-73893
08/15/2018, 6:00 PMadamant-restaurant-73893
08/15/2018, 6:00 PMadamant-restaurant-73893
08/15/2018, 6:01 PMadamant-restaurant-73893
08/15/2018, 6:01 PM