steep-beach-52652
11/16/2021, 1:10 PM<https://github.com/pulumi/pulumi/blob/master/docker/pulumi/Dockerfile>
gorgeous-minister-41131
11/16/2021, 7:06 PMbitter-island-28909
11/16/2021, 7:47 PMswift-intern-18856
11/16/2021, 8:54 PMerror: post-step event returned an error: failed to save snapshot: .pulumi/stacks/base.non-prod.json: snapshot integrity failure; it was already written, but is invalid (backup available at .pulumi/stacks/base.non-prod.json.bak): resource urn:pulumi:base.non-prod::yd-base::yd:eks:Cluster$eks:index:Cluster$kubernetes:core/v1:ConfigMap::yd-eks-nodeAccess refers to unknown provider urn:pulumi:base.non-prod::yd-base::yd:eks:Cluster$eks:index:Cluster$pulumi:providers:kubernetes::yd-eks-eks-k8s::b48893e2-fd53-4bed-9753-c28de972084c
i think i understand the error (the provider was deleted when the cluster was replaced), but unsure how to resolve restoring the backup, any tips?gifted-salesmen-8201
11/16/2021, 9:12 PMlimited-electrician-71574
11/16/2021, 9:45 PMfast-rain-29589
11/17/2021, 3:21 AM--cache-from
when using docker.Image
to run a build?colossal-boots-62227
11/17/2021, 3:47 AMtall-beard-99429
11/17/2021, 10:09 AMerror: performing HTTP request: Get "<https://api.pulumi.com/api/stacks/jobilla/environments/staging>": dial tcp: lookup <http://api.pulumi.com|api.pulumi.com>: no such host
make: *** [Makefile:41: staging-update] Error 255
tall-beard-99429
11/17/2021, 10:09 AMfreezing-kite-2503
11/17/2021, 10:16 AMpulumi new azure-typescript
seems the Install Dependencies step blocks on extracting the following package: extract:es-abstract: sill extract es-abstract@^1.19.1
. I have been waiting for close to 20 min now, in hope that is just slow, but nothing happens....mammoth-journalist-45153
11/17/2021, 2:50 PMoriginal_src_path = /path/to/origObj
new_src_path = /path/to/newObjWhen I execute pulumi up and select details, I see 3 actions are about to be done:
++awss3/objectCopyObjectCopy: (create-replacement)
+-awss3/objectCopyObjectCopy: (replace)
--awss3/objectCopyObjectCopy: (delete-replaced)When I execute them, they happen in order, i.e. create, replace, delete. Thing is, the delete is deleting the newly created file (which has the same path), so I'm left with an empty bucket. To emphasize - create-replacement creates the object, but it's subsequently deleted. Question is, what am I doing wrong?
steep-beach-52652
11/17/2021, 2:54 PMrapid-raincoat-36492
11/17/2021, 3:45 PMterraform {
required_providers {
pulumi = {
version = "0.0.2"
source = "<http://hashicorp.com/transcend-io/pulumi|hashicorp.com/transcend-io/pulumi>"
}
}
}
provider "pulumi" {}
data "pulumi_stack_outputs" "stack_outputs" {
organization = "transcend-io"
project = "some-pulumi-project"
stack = "dev"
}
output "version" {
value = data.pulumi_stack_outputs.stack_outputs.version
}
output "stack_outputs" {
value = data.pulumi_stack_outputs.stack_outputs.stack_outputs
}
This code has helped my company transition our large terraform codebase to a hybrid model using both terraform and pulumi, and the source is available here: https://github.com/transcend-io/terraform-provider-pulumi
I'll be writing a blog post soon about our strategy in the migration as wellmillions-lunch-7967
11/17/2021, 6:38 PMresource "google_composer_environment" "test" {
name = "example-composer-env"
region = "us-central1"
config {
node_count = 4
node_config {
zone = "us-central1-a"
machine_type = "n1-standard-1"
network = google_compute_network.test.id
subnetwork = google_compute_subnetwork.test.id
service_account = google_service_account.test.name
}
database_config {
machine_type = "db-n1-standard-2"
}
web_server_config {
machine_type = "composer-n1-webserver-2"
}
}
}
millions-lunch-7967
11/17/2021, 6:39 PMmillions-lunch-7967
11/17/2021, 6:39 PMmicroscopic-ram-86765
11/17/2021, 9:58 PMgithub
provider. I may be missing something obvious here, but there doesn't seem to be a way to set a RepositoryEnvironment
to only allow a branch like you can via the UI (screenshot attached).
There's an option to create a policy, but the policy is only a boolean
to turn it on or off with no way to specify the actual branch policy.
https://www.pulumi.com/registry/packages/github/api-docs/repositoryenvironment/#custombranchpolicies_nodejs
customBranchPolicies This property is required.
boolean
Whether only branches that match the specified name patterns can deploy to this environment.
purple-plumber-90981
11/17/2021, 11:54 PMsteep-beach-52652
11/18/2021, 12:52 PMsquare-coat-62279
11/18/2021, 2:07 PM{
"data":
"test.json": |
{
"maxThreadCount": 10,
"trackerConfigs": [{
"url": "<https://example1.com/>",
"username": "username",
"password": "password",
"defaultLimit": 1
}
}
}
powerful-furniture-83753
11/18/2021, 2:37 PMable-camera-57198
11/18/2021, 7:44 PMbillions-xylophone-85957
11/18/2021, 7:48 PMpulumi state delete
?
Let's say I royally screwed up and ended up deleting some resource that has a lot of children, e.g. a k8s cluster. Now my Pulumi state is horribly broken as pulumi state delete
isn't really helpful since there are far too many dependencies to walk the tree myself from down up. In this situation it would be really great to have --yes-i-know-what-i-am-doing
flag to pulumi state delete
to force the deletes to cascade. After all, my root resource is not there anymore and the resources in the state do not correlate with the actual infrastructure objects anyway.
wdyt?gorgeous-minister-41131
11/18/2021, 8:05 PMable-camera-57198
11/19/2021, 12:00 AMbest-lifeguard-91445
11/19/2021, 2:27 AMcolossal-boots-62227
11/19/2021, 3:37 AMpyenv
and poetry
) which works well on 3.17.1
fierce-nightfall-86468
11/19/2021, 7:46 AMfierce-nightfall-86468
11/19/2021, 7:47 AM