icy-jordan-58549
04/29/2021, 1:08 PMwarning: #1 [internal] load build definition from Dockerfile
full-artist-27215
04/29/2021, 2:47 PMpulumi_aws.iam.get_role
(using Python, FWIW) in order to grant it permission to access an S3 bucket. The stack creation and permission granting are currently in the initialization of a Component Resource. As I was developing my application, I started out with just the CloudFormation stack, and only later added this permission granting step. Because of this, the CloudFormation stack (and thus the Role) already existed by the time I added the get_role
call. Now, however, I am creating a new instance of my Pulumi stack from scratch, and nothing exists. I had assumed that my get_role
call would be fine, given that I'm using the Outputs of the CloudFormation stack, e.g.
queue_instance_role = aws.iam.get_role(
name=self.cf_stack.outputs["InstanceRoleName"],
)
but this apparently isn't sufficient; I'm getting the following error:
Exception: invoke of aws:iam/getRole:getRole failed: Missing required argument: The argument "name" is required, but no definition was found. ()
This is on Pulumi 2.25.2.
Is there a way to force this get_role
call to wait until the CloudFormation stack is created before being invoked? Thanks.colossal-australia-65039
04/30/2021, 12:02 AMcuddly-carpenter-20638
04/30/2021, 12:05 AMUpdating (dev):
Type Name Status Info
pulumi:pulumi:Stack pulumi-starter-dev **failed** 1 error
+ └─ kubernetes:apps/v1:Deployment nginx **creating failed** 1 error
Diagnostics:
pulumi:pulumi:Stack (pulumi-starter-dev):
error: update failed
kubernetes:apps/v1:Deployment (nginx):
error: resource nginx-uzv9l9j4 was not successfully created by the Kubernetes API server : deployments.apps is forbidden: User "me" cannot create resource "deployments" in API group "apps" in the namespace "default"
cuddly-carpenter-20638
04/30/2021, 12:07 AMnamespace
called pulumi-starter
that I’m trying to deploy this in, but it keeps trying to deploy to default
kubectl get po
No resources found in pulumi-starter namespace.
cuddly-carpenter-20638
04/30/2021, 12:07 AM"use strict";
const k8s = require("@pulumi/kubernetes");
const appLabels = { app: "nginx" };
const deployment = new k8s.apps.v1.Deployment("nginx", {
spec: {
selector: { matchLabels: appLabels },
replicas: 1,
template: {
metadata: { labels: appLabels },
spec: { containers: [{ name: "nginx", image: "nginx:alpine" }] }
}
}
});
exports.name = deployment.metadata.name;
cuddly-carpenter-20638
04/30/2021, 12:36 AMcuddly-actor-99406
04/30/2021, 2:41 AMpulumi up
now throws with a not very useful stack trace. It's throwing from pulumi.runtime.rpc.serialize_property
. I put in some debug print statements and I think it is k8s.yaml.ConfigFile
which is the resource involved. It looks like it might be related to something in the upgrade notes "*snake_case/camelCase Key Translation Fixes in Provider Python SDKs*". Can anyone help?gifted-island-55702
04/30/2021, 7:36 AMbumpy-agent-19616
04/30/2021, 10:22 AMerror: failed to load checkpoint: blob (key ".pulumi/stacks/identity-test.json") (code=Unknown): -> <http://github.com/Azure/azure-storage-blob-go/azblob.newStorageError|github.com/Azure/azure-storage-blob-go/azblob.newStorageError>, /Users/runner/go/pkg/mod/github.com/!azure/azure-storage-blob-go@v0.13.0/azblob/zc_storage_error.go:42
===== RESPONSE ERROR (ServiceCode=AuthorizationFailure) =====
Description=This request is not authorized to perform this operation.
RequestId:83e63fd7-e01e-0005-0c6e-3d938c000000
Time:2021-04-30T03:09:34.4679001Z, Details:
Code: AuthorizationFailure
GET https://**************.<http://blob.core.windows.net/*********/.pulumi/stacks/identity-test.json?timeout=61|blob.core.windows.net/*********/.pulumi/stacks/identity-test.json?timeout=61>
Authorization: REDACTED
User-Agent: [go-cloud/blob/0.1.0 Azure-Storage/0.13 (go1.16.3; linux)]
X-Ms-Client-Request-Id: [80971ac2-1589-4582-4251-041bdeb5f1da]
X-Ms-Date: [Fri, 30 Apr 2021 03:09:34 GMT]
X-Ms-Version: [2019-12-12]
--------------------------------------------------------------------------------
RESPONSE Status: 403 This request is not authorized to perform this operation.
Content-Length: [246]
Content-Type: [application/xml]
Date: [Fri, 30 Apr 2021 03:09:33 GMT]
Server: [Microsoft-HTTPAPI/2.0]
X-Ms-Client-Request-Id: [80971ac2-1589-4582-4251-041bdeb5f1da]
X-Ms-Error-Code: [AuthorizationFailure]
X-Ms-Request-Id: [83e63fd7-e01e-0005-0c6e-3d938c000000]
Any help would be much appreciated.shy-football-10348
04/30/2021, 4:41 PMbillowy-laptop-45963
04/30/2021, 4:52 PMtall-scientist-89115
04/30/2021, 7:40 PMnew pulumi.Config()
yielded:
throw new Error("Program run without the Pulumi engine available; re-run using the `pulumi` CLI");`
many-psychiatrist-74327
04/30/2021, 8:27 PM[secret]
?
Context: I’m following this guide to create a GKE kubernetes cluster. The code (copy pasted from the example) generates a kubeconfig by combining the outputs of the cluster resource. I want to export the kubeconfig so I can use kubectl
against it, but it just prints out as [secret]
. Why?hallowed-rain-9096
04/30/2021, 9:10 PMmany-psychiatrist-74327
04/30/2021, 9:46 PMk8s.yaml.ConfigFile
name unique, its sub-resources will have the same names and conflict. I tried using a transformation
option that renames the resources (adding a prefix), but that seems to be ignored by pulumi and the URN conflicts persist. I would’ve thought that the object hierarchy would make the URNs unique, but it doesn’t seem to do so.
Any ideas?gorgeous-minister-41131
04/30/2021, 11:25 PMworried-knife-31967
05/01/2021, 2:40 PMtall-scientist-89115
05/01/2021, 9:31 PMazure.keyvault.getSecret
inside the automation api? I keep getting
Error: Program run without the Pulumi engine available; re-run using the `pulumi` CLI
lemon-monkey-228
05/02/2021, 7:38 AMlemon-monkey-228
05/02/2021, 7:38 AMconfig.require("gcp:project")
lemon-monkey-228
05/02/2021, 7:38 AMlemon-monkey-228
05/02/2021, 8:25 AMboundless-angle-56560
05/02/2021, 8:42 AMworried-knife-31967
05/02/2021, 9:11 AMlemon-monkey-228
05/02/2021, 6:22 PMpulumi up
)?lemon-monkey-228
05/02/2021, 6:22 PMGOOGLE_CREDENTIALS
, that’s what it wants to use for the lotlemon-monkey-228
05/02/2021, 6:22 PMfresh-hospital-81544
05/03/2021, 12:15 AMconst repo = new awsx.ecr.Repository("registry");
const image = repo.buildAndPushImage('/path/to/image');
I notice each time I run pulumi up the image is getting built and pushed (hits the cache so the time delay isn't too bad but still unnecessary to run these steps every time). Is there a way to skip this altogether if the image directory has not changed?
thanksbetter-shampoo-48884
05/03/2021, 7:32 AMparent
?better-shampoo-48884
05/03/2021, 7:32 AMparent
?bored-oyster-3147
05/03/2021, 11:24 AMlittle-cartoon-10569
05/03/2021, 8:45 PM