stale-vase-87890
03/24/2022, 5:19 PMexport const devopsUserIds = pulumi.output(devopsUsers).apply(userlist => userlist.map((user: { id: any }) => user.id))
This produces
+ devopsUserIds : [
+ [0]: "00uyn0nldHI1SFLwasdfasd"
+ [1]: "00uyq0314ehGvU12121"
]
Somehow I am unable to extract it to something more like this
devopsUserIds['00uyn0nldHI1SFLwasdfasd', '00uyq0314ehGvU12121']
future-fountain-86701
03/24/2022, 5:37 PMpulumi config set
but both approach don’t seem to work. Let me know if I’m missing something obvious 😅stale-vase-87890
03/24/2022, 7:00 PM[ 'bar', 'cat'] and one called bar: ['abc,' '123]. that I would like to make into flat: ['bar", "cat", "abc", "123"]
early-telephone-30941
03/24/2022, 8:01 PMswift-advantage-57448
03/24/2022, 8:15 PMadorable-action-51248
03/24/2022, 8:20 PMbig-potato-91793
03/24/2022, 9:10 PMTypeError: Invalid Version:
at new SemVer (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:332:11)
at compare (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:647:10)
at Function.eq (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:693:10)
at sameVersion (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:703:57)
at register (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:718:17)
at Object.registerResourcePackage (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:780:5)
at Object.<anonymous> (/builds/${PROJECT}/pulumi/node_modules/@ticketmaster/pipelog-crds/build/index.js:25:16)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
colossal-river-93017
03/25/2022, 12:57 AMpulumi up
error: Program failed with an unhandled exception:
error: Traceback (most recent call last):
File "~/.pulumi/bin/pulumi-language-python-exec", line 107, in <module>
loop.run_until_complete(coro)
File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 126, in run_in_stack
await run_pulumi_func(lambda: Stack(func))
File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 51, in run_pulumi_func
await wait_for_rpcs()
File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 110, in wait_for_rpcs
raise exception
File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 169, in run
value = await self._future
File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 169, in run
value = await self._future
File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 194, in run
transformed: Input[U] = func(value)
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/image.py", line 254, in <lambda>
lambda args: get_image_data(_ImageArgs(*args))
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/image.py", line 231, in get_image_data
unique_target_name = build_and_push_image(
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 243, in build_and_push_image
build_result = build_image(base_image_name, path_or_build, log_resource, cache_from)
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 437, in build_image
docker_build(image_name, build, log_resource, cache_from)
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 491, in docker_build
return run_command_that_must_succeed("docker", build_args, log_resource, env=build.env)
File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 608, in run_command_that_must_succeed
raise ResourceError(
pulumi_docker.docker.ResourceError: 'docker build -t backend:dev ~/project/app/backend' failed with exit code 1
error: an unhandled error occurred: Program exited with non-zero exit code: 1
dry-salesmen-32588
03/25/2022, 8:15 AMred-football-97286
03/25/2022, 9:24 AMrough-intern-34947
03/25/2022, 12:58 PMadorable-gpu-98268
03/25/2022, 2:25 PM.git
folder to Pulumi in GitHub Actions. Still I do not get a comment by the GitHub App. What could be the problem? I have a setup that does reproducible builds in containers, so there is no implicit access to the environment variables in github actions. Which ones do I have to forward?magnificent-noon-74840
03/25/2022, 3:52 PMpolite-napkin-90098
03/25/2022, 4:42 PM_, err = helm.NewChart(ctx, "influx", helm.ChartArgs{
Repo: pulumi.String("influxdata"),
Chart: pulumi.String("influxdb2"),
Values: pulumi.Map{
"storageClass": pulumi.String("efs-stor"),
},
},
pulumi.ProviderMap(map[string]pulumi.ProviderResource{
"kubernetes": eksProvider,
}),)
if err != nil {
return err
}
But when I run pulumi up, there is no StorageClassName set in the PVC spec:
+ kubernetes:core/v1:PersistentVolumeClaim: (create)
[urn=urn:pulumi:influx-test::influx::kubernetes:<http://helm.sh/v3:Chart$kubernetes:core/v1:PersistentVolumeClaim::influx-influxdb2|helm.sh/v3:Chart$kubernetes:core/v1:PersistentVolumeClaim::influx-influxdb2>]
[provider=urn:pulumi:influx-test::influx::pulumi:providers:kubernetes::eksprov::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
apiVersion: "v1"
kind : "PersistentVolumeClaim"
metadata : {
annotations: {
<http://helm.sh/resource-policy|helm.sh/resource-policy>: "keep"
}
labels : {
<http://app.kubernetes.io/instance|app.kubernetes.io/instance> : "influx"
<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
<http://app.kubernetes.io/name|app.kubernetes.io/name> : "influxdb2"
<http://app.kubernetes.io/version|app.kubernetes.io/version> : "2.1.1"
<http://helm.sh/chart|helm.sh/chart> : "influxdb2-2.0.10"
}
name : "influx-influxdb2"
namespace : "default"
}
spec : {
accessModes: [
[0]: "ReadWriteOnce"
]
resources : {
requests: {
storage: "50Gi"
}
}
}
Can anyone see what I'm doing wrong? Or is this the wrong channel for this? Should I go and speak to influx or helm?busy-telephone-91852
03/25/2022, 8:58 PMerror: could not load plugin for aws provider 'urn:pulumi:plane-2::launchpad::pulumi:providers:aws::aws-provider': could not read plugin [/nix/store/d26ir9idflpfn2rb9x4w8z4xvhz9mqah-pulumi-3.26.1/bin/pulumi-resource-aws] stdout: EOF
rough-oyster-77458
03/26/2022, 1:26 AMpulumi import [type] [name] [id]
command. How can I get type
for my resources?rough-oyster-77458
03/27/2022, 11:52 PMpulumi import gcp:storage/bucketIAMMember:BucketIAMMember disk1_iam_member "disk1--bucket--name roles/storage.Admin user:user1@example.com"
And I get this error message:
error: Preview failed: importing disk1--bucket--name roles/storage.Admin user:ab@playa.tech: Cannot find binding for "storage bucket \"b/disk1--data--sandbox--playa-tech\"" with role "roles/storage.Admin", member "user:user1@example.com", and condition title ""
So, it says that no such binding for this user. For me, this message looks odd because I'm pretty sure user1
has a Storage Admin role for bucket disk1--bucket--name
. I have just checked this in GCP console.
Any ideas what I'm doing wrong? Tnx guys in advancerough-oyster-77458
03/27/2022, 11:53 PMhelpful-account-44059
03/28/2022, 7:30 AMkubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-webhook:subjectaccessreviews):
error: resource cert-manager-webhook:subjectaccessreviews was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-webhook:subjectaccessreviews" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:RoleBinding|rbac.authorization.k8s.io/v1:RoleBinding> (cert-manager/cert-manager-webhook:dynamic-serving):
error: resource cert-manager/cert-manager-webhook:dynamic-serving was not successfully created by the Kubernetes API server : <http://rolebindings.rbac.authorization.k8s.io|rolebindings.rbac.authorization.k8s.io> "cert-manager-webhook:dynamic-serving" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-view):
error: resource cert-manager-view was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-view" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-ingress-shim):
error: resource cert-manager-controller-ingress-shim was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-ingress-shim" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-orders):
error: resource cert-manager-controller-orders was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-orders" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-issuers):
error: resource cert-manager-controller-issuers was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-issuers" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:RoleBinding|rbac.authorization.k8s.io/v1:RoleBinding> (kube-system/cert-manager:leaderelection):
error: resource kube-system/cert-manager:leaderelection was not successfully created by the Kubernetes API server : <http://rolebindings.rbac.authorization.k8s.io|rolebindings.rbac.authorization.k8s.io> "cert-manager:leaderelection" already exists
kubernetes:apps/v1:Deployment (cert-manager/cert-manager):
error: resource cert-manager/cert-manager was not successfully created by the Kubernetes API server : deployments.apps "cert-manager" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-clusterissuers):
error: resource cert-manager-controller-clusterissuers was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-clusterissuers" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-challenges):
error: resource cert-manager-controller-challenges was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-challenges" already exists
kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io>):
error: resource <http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io>" already exists
kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io>):
error: resource <http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io>" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-certificatesigningrequests):
error: resource cert-manager-controller-certificatesigningrequests was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-certificatesigningrequests" already exists
kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration> (cert-manager-webhook):
error: resource cert-manager-webhook was not successfully created by the Kubernetes API server : <http://mutatingwebhookconfigurations.admissionregistration.k8s.io|mutatingwebhookconfigurations.admissionregistration.k8s.io> "cert-manager-webhook" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-certificates):
error: resource cert-manager-controller-certificates was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-certificates" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-challenges):
error: resource cert-manager-controller-challenges was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-challenges" already exists
kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://orders.acme.cert-manager.io|orders.acme.cert-manager.io>):
error: resource <http://orders.acme.cert-manager.io|orders.acme.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://orders.acme.cert-manager.io|orders.acme.cert-manager.io>" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-edit):
error: resource cert-manager-edit was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-edit" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-certificates):
error: resource cert-manager-controller-certificates was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-certificates" already exists
kubernetes:apps/v1:Deployment (cert-manager/cert-manager-webhook):
error: resource cert-manager/cert-manager-webhook was not successfully created by the Kubernetes API server : deployments.apps "cert-manager-webhook" already exists
kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-orders):
error: resource cert-manager-controller-orders was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-orders" already exists
astonishing-notebook-93377
03/28/2022, 8:17 AMastonishing-energy-53370
03/28/2022, 11:03 AMalert-zebra-27114
03/28/2022, 11:49 AMpurple-kilobyte-1629
03/28/2022, 5:14 PMpulumi.Config
cross stacks? If not, is there an option to go around it in a clean way?billowy-horse-79629
03/28/2022, 5:33 PMpanic: fatal: An assertion has failed
- in addition, there’s nothing in the values.yaml file that relates to these values.
Here’s a screenshot of the code segment:kind-island-70054
03/28/2022, 5:46 PMpulumi stack ls
shows both stacks when I thought it should only show the stacks from the current project by default. The -p option does not change anything. Using pulumi stack select theoneintheotherdirectory
creates a new yaml file…
Is that expected?astonishing-quill-88807
03/28/2022, 6:19 PMmany-psychiatrist-74327
03/28/2022, 6:32 PMpulumi refresh
, every subsequent pulumi preview
fails because the diff wants to delete-and-recreate the cluster, so it fails because the cluster is protected.
However, pulumi doesn’t tell me why it wants to recreate the cluster. There’s no “details” to observe because the preview fails. So I have no idea how to edit the state or the code to bring everything back in sync.
Is there a way to find out that information out of pulumi?thankful-coat-47937
03/28/2022, 10:27 PMbusy-island-31180
03/29/2022, 3:24 AMpull_request
resource?
https://www.pulumi.com/registry/packages/github/api-docs/repositorypullrequest/
https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_pull_request
This one seems a bit weird. Like you’d have to constantly be adding resources to a stack (new pull requests), or you need to automatically “forget” the resource, so you can recreate it? (pulumi state rm
)
I’m curious if anyone has used this before, and how they are using it.ancient-energy-2517
03/29/2022, 7:55 AMancient-energy-2517
03/29/2022, 7:55 AM