lemon-machine-35564
02/05/2021, 11:31 PMstack delete <urn>
says it doesn’t existsquare-art-73366
02/06/2021, 12:44 AMbored-oyster-3147
02/07/2021, 6:09 PMwet-soccer-72485
02/07/2021, 6:26 PMcold-motherboard-287
02/08/2021, 8:50 AMjson
or a yaml
file I suppose. Is there a workaround for it?
Another option would be to implement another secrets/config provider altogether, but I also didn't find any information on how to do it.wide-crayon-4093
02/08/2021, 10:16 AMistioctl operator install
and then install istio itself via manifest. here, I'm not sure where to startcolossal-rainbow-39841
02/08/2021, 1:20 PMfreezing-quill-32178
02/08/2021, 2:27 PM@pulumi/gcp
and the underlying terraform-provider
don’t support yet the SQL import from GCP bucket.
Currently i’ve created my own shell scripts utilising gcloud sql import cli but i want to make the whole deployment flow with Pulumi as well as put it in GitLab CI/CD.
Any suggestion is welcomed! Thanksbored-oyster-3147
02/08/2021, 4:21 PMcompleting deletion from previous update
on an ACM Certificate that can't be deleted due to "certificate is in use" error whenever I try to pulumi destroy
. Any idea how to clear or reset this pending deletion?average-school-38756
02/08/2021, 6:02 PMcolossal-australia-65039
02/09/2021, 12:02 AMStackReference
to the test
stack with everything using the same S3 backend but I run into this error
pulumi:pulumi:StackReference (test):
error: Preview failed: decrypting secret value: failed to decrypt: incorrect passphrase, please set PULUMI_CONFIG_PASSPHRASE to the correct passphrase
I can't find documentation on how to resolve this. I've tried exporting PULUMI_CONFIG_PASSPHRASE
as the one for test
instead of my current stack, but then i get another error since the secrets password for the current stack is mismatchinggifted-terabyte-92288
02/09/2021, 1:17 AMpulumi stack select
or pulumi refresh
I get the following:
error: invalid character '"' after top-level value
Some commands work though - like pulumi stack ls
(but I can't then switch to any of the stacks). I have tried uninstall and re-installing the cli (brew remove pulumi
| brew install pulumi
), but between installations it remembers who I am. I'm assuming there's some cached configuration that is corrupted - any idea where that file may be (I checked Homebrew cache)?ambitious-father-68746
02/09/2021, 2:04 AMpulumi pre
is over in a minute, but the smallest change with pulumi up
, like updating just one resource, doesn't matter which, takes more than 30 minutes to run. This happens even if I use -t
. My backend is AWS. I've enabled some verbose logging and there is a lot of incoming output value translated
and incoming output property translated
, it seems to be covering the whole of the stack, once again even with -t
. It ends with a waiting for quiescence
with a counter on the upper hundreds going to zero, which I can't seem to be able to even find on Google. It almost feels like the whole of the stack is being processed even though there is a single change to be made. I'm not sure how to progress from here, having to wait between 30 minutes to an 1+ hour just to add an environment variable to a service is killing us. Any ideas? Thank you.wide-crayon-4093
02/09/2021, 3:46 AMindex.ts
? super excited to be moving my infra to code. for now I'm just procedurally dumping my resources in a single file, but want to eventually structure and modularize it properly. what I'm most interested in is passing dependencies and context around. (e.g k8s provider)echoing-activity-32278
02/09/2021, 11:15 AMnarrow-battery-9106
02/09/2021, 12:21 PMspec:
group: tekton.dev
preserveUnknownFields: false
versions:
- &version
name: v1alpha1
served: true
storage: false
# Opt into the status subresource so metadata.generation
# starts to increment
subresources:
status: {}
schema:
openAPIV3Schema:
type: object
# One can use x-kubernetes-preserve-unknown-fields: true
# at the root of the schema (and inside any properties, additionalProperties)
# to get the traditional CRD behaviour that nothing is pruned, despite
# setting spec.preserveUnknownProperties: false.
#
# See <https://kubernetes.io/blog/2019/06/20/crd-structural-schema/>
# See issue: <https://github.com/knative/serving/issues/912>
x-kubernetes-preserve-unknown-fields: true
- !!merge <<: *version
name: v1beta1
storage: true
names:
kind: Pipeline
plural: pipelines
categories:
- tekton
- tekton-pipelines
scope: Namespaced
conversion:
strategy: Webhook
webhook:
conversionReviewVersions: ["v1beta1"]
clientConfig:
service:
name: tekton-pipelines-webhook
namespace: tekton-pipelines
I presume problem is with !!merge and &version thing but I am not surenarrow-battery-9106
02/09/2021, 12:50 PMbig-potato-91793
02/09/2021, 4:10 PMbig-potato-91793
02/09/2021, 4:10 PMicy-jordan-58549
02/09/2021, 4:23 PMpulumi
is currently running in preview
mode ?glamorous-van-94517
02/09/2021, 5:05 PMclever-lawyer-94920
02/09/2021, 5:39 PMaverage-school-38756
02/09/2021, 9:08 PMred-football-97286
02/10/2021, 11:44 AMbroad-dog-22463
02/10/2021, 11:45 AMred-football-97286
02/10/2021, 11:45 AMquiet-lock-69596
02/10/2021, 12:51 PMbroad-dog-22463
02/10/2021, 1:04 PMgorgeous-beach-44078
02/10/2021, 2:00 PM@prisma/client
not initialising.
A simular issue is found within serverless
, where the main issue was webpack running another yarn install prior to packaging, which was not running my prisma generate properly. This caused my @prisma/client to be either empty, or at least not include the required binaries.
The solution when using serverless
would be to create an custom webpack. How would I solve the same issue in pulumi?wide-crayon-4093
02/10/2021, 2:58 PMdefault
namespace from k8s? I did an import, but if I delete the k8s cluster it will try to remove the default namespace first, which is not possible.