big-potato-91793
01/26/2020, 7:32 PMmysterious-egg-7415
01/26/2020, 7:33 PMbright-orange-69401
01/27/2020, 11:58 AMnice-guitar-97142
01/27/2020, 5:58 PMpulumi stack init
command with a --secrets-provider
arg and it’s just sitting there with no logging or anything. i attempted to also run with -v 4
arg to no avail. what do i need to do to get some kind of logging to tell me why this command isn’t working? if it helps, I am using azurekeyvault, the key is RSA-2048, and the whole command looks like
pulumi stack init MyOrganization/dev --secrets-provider="<azurekeyvault://my-kv-name.vault.azure.net/keys/pulumi-secrets>"
future-morning-96441
01/27/2020, 8:07 PMpulumi up
?
I'm facing long deployment times and the CI ran out of memory at several occations (currently memory is set to 4GB, I believe).swift-painter-31084
01/27/2020, 9:28 PMSECONDARY
. A PRIMARY
record will be served if its healthcheck is passing, otherwise the SECONDARY
will be served." however all examples I've found show Type indicating the record type, ie "CNAME", "A", etc.handsome-actor-1155
01/27/2020, 11:12 PMpulumi new <template>
and instantiate with default complex configsgreat-vr-65723
01/28/2020, 12:19 AMpulumi up
that might take 30 minutes, about half way through Pulumi will lose access to the S3 bucket backend, and then it gets all sorts of confused.
Is there any way to launch asynchronous deployments with a non-SaaS backend?
With CloudFormation, it submits the stack to AWS and runs asynchronously, so your token only needs to be valid for the length of time it takes to run CreateStack
or UpdateStack
. I'm kind of hoping for something similar for Pulumi.able-crayon-21563
01/28/2020, 9:22 AMable-crayon-21563
01/28/2020, 9:23 AMpulumi.ComponentResource
.faint-motherboard-95438
01/28/2020, 10:35 AMIngress
in my clusters which was working fine before but now when I create/update I got an error like :
error: creation of resource […] failed because the Kubernetes API server reported that the apiVersion for this resource does not exist. Verify that any required CRDs have been created: no matches for kind “Ingress” in version “networking.k8s.io/v1beta1”I create the resource like
new pulumi_kubernetes.networking.v1beta1.Ingress()
I tried to switch to `pulumi_kubernetes.networking.v1.Ingress`but I got a type error that Ingress
does not exist in networking.v1
My versions :
“@pulumi/kubernetes”: “1.4.1",
“@pulumi/pulumi”: “1.9.0",
kubectl version :
Client Version: version.Info{Major:“1”, Minor:“17", GitVersion:“v1.17.2”, GitCommit:“59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:“clean”, BuildDate:“2020-01-23T14:21:54Z”, GoVersion:“go1.13.6”, Compiler:“gc”, Platform:“darwin/amd64”}
Server Version: version.Info{Major:“1", Minor:“13+“, GitVersion:“v1.13.11-gke.14”, GitCommit:“56d89863d1033f9668ddd6e1c1aea81cd846ef88", GitTreeState:“clean”, BuildDate:“2019-11-07T19:12:22Z”, GoVersion:“go1.12.11b4”, Compiler:“gc”, Platform:“linux/amd64”}
I suppose that’s a problem between pulumi packages version and the kubernetes server api but I can’t find a match between them both now.
I also tried to downgrade @pulumi/kubernetes
without any success.bitter-dentist-28132
01/28/2020, 2:29 PMboundless-monkey-50243
01/28/2020, 4:11 PMsparse-intern-71089
01/28/2020, 4:29 PMmany-lock-25065
01/28/2020, 7:23 PM<type>-<name>
?)stocky-student-96739
01/28/2020, 7:41 PMmany-lock-25065
01/28/2020, 7:55 PMgentle-bird-84737
01/28/2020, 8:20 PMfresh-daybreak-17893
01/28/2020, 10:29 PMpulumi preview
working on their workstations. This isn't currently the case since some team members have already upgraded to 1.9.1, which is the version exhibiting the unwanted behavior, while some others are on 1.8.1 which still works for our use case.fresh-daybreak-17893
01/28/2020, 10:29 PMrm
the ~/.pulumi
directory, download the 1.8.1 tarball from https://www.pulumi.com/docs/get-started/install/versions/ then extract the tarball and put extracted binaries somewhere on $PATH. Is there anything else we should watch out for?colossal-ram-89482
01/29/2020, 12:31 AMsilly-dusk-21491
01/29/2020, 11:24 AMambitious-crayon-56788
01/29/2020, 4:41 PMZipBlob
resource, but without the blob that was previously created being deleted after every run of pulumi up
.
Each blob is uniquely named.
I have discovered CustomResourceOptions
, and from those options I've used deleteBeforeReplace: false
, assuming this would stop to resource being deleted before it was replaced. However, this is not the case, and the blob previously created by the Pulumi resource is still deleted.
How can I keep blobs previously created by the Pulumi resource?
const zipBlob = new azure.storage.ZipBlob("storageBlob", {
name: `MyApp.${version}.zip`,
storageAccountName: storageAccount.name,
storageContainerName: storageContainerForReleases.name,
type: "block",
content: new pulumi.asset.FileArchive("MyFileArchive"),
}, {
deleteBeforeReplace: false
});
I have also tried to use the CustomResourceOptions
of protect
, but this caused the pulumi up
operation to fail because Pulumi still tries to delete the resource, but can't because of the protection.thankful-optician-22583
01/29/2020, 5:04 PMcuddly-australia-15715
01/29/2020, 8:20 PMcuddly-australia-15715
01/29/2020, 8:23 PMadventurous-park-10099
01/29/2020, 8:37 PMcold-motorcycle-78950
01/30/2020, 12:40 PMcalm-parrot-97479
01/30/2020, 12:49 PMbitter-dentist-28132
01/30/2020, 3:18 PMbitter-dentist-28132
01/30/2020, 3:18 PMgreen-school-95910
01/30/2020, 5:34 PMbitter-dentist-28132
01/30/2020, 5:37 PMthankful-optician-22583
01/30/2020, 6:13 PMexport const appTag ='your image tag';
before I run pulumi update, I query the output file like this
export PREV_APP_TAG=$(pulumi stack output -j | jq '.appTag')
And then if my update fails, i set this
pulumi config set app:tag $PREV_APP_TAG
and then run a pulumi update again.green-school-95910
01/30/2020, 6:15 PMthankful-optician-22583
01/30/2020, 6:16 PMgreen-school-95910
01/30/2020, 6:17 PMthankful-optician-22583
01/30/2020, 6:21 PMbig-caravan-87850
01/30/2020, 6:32 PMgreen-school-95910
01/30/2020, 6:33 PMbig-caravan-87850
01/30/2020, 7:35 PMgentle-diamond-70147
01/30/2020, 8:30 PMup
to achieve rollback. More explanation is at https://www.pulumi.com/docs/troubleshooting/faq/#does-pulumi-support-automatic-rollback-in-the-event-of-an-error-or-failure.bitter-dentist-28132
01/30/2020, 10:19 PMgreen-school-95910
01/30/2020, 10:26 PMbitter-dentist-28132
01/31/2020, 7:55 PMgentle-diamond-70147
01/31/2020, 8:05 PMbitter-dentist-28132
01/31/2020, 8:10 PMgentle-diamond-70147
01/31/2020, 8:13 PMi guess a more broad question would be, how do you ensure you don't break prod?One of our engineers did a talk on exactly that recently! 🙂 https://twitter.com/PulumiCorp/status/1221843815872499713