enough-truck-34175
05/13/2021, 11:31 PMlittle-cartoon-10569
05/14/2021, 4:45 AMwarning: urnpulumistackprojectaws:PublicProxy$cloudinitindex/configConfig::stack verification warning: Deprecated ResourceI can't see it in the code anywhere, and there's no additional info.
gorgeous-country-43026
05/14/2021, 9:31 AMastonishing-monitor-96741
05/14/2021, 12:26 PMecrblahblah/repo:38989f9f92096e33d3d8505a833f7cf4aaf30a12afec448f895394aefc1e4372-570125e6816fe0b91a5e7c432a3cc0581d864ad49a3f68a7074e00369321cac4
orange-lawyer-86718
05/14/2021, 12:33 PMbig-architect-71258
05/14/2021, 6:55 PMpulumi preview
.
https://github.com/pulumi/pulumi-azure/issues/890green-knife-34770
05/15/2021, 2:22 PMawsx.ecs.Image.fromDockerBuild
and when the image gets running on AWS it throws standard_init_linux.go:219: exec user process caused: exec format error
. So I found this article where using dockers buildx resolves the issue. My question is, how can I use buildx with pulumi? (Even better exactly within awsx.ecs.Image.fromDockerBuild
) I saw only mention for a new Pulumi blog article exactly about that, but it hasn’t come up yet. Thank you for your time!brash-airline-37413
05/15/2021, 10:24 PMchilly-night-36370
05/16/2021, 11:10 AMazure-nextgen
to azure-native
and it wants to re-create the resource group. Is there a way I can force pulumi to think those are the same resource groups?clever-lawyer-94920
05/16/2021, 5:46 PMclever-lawyer-94920
05/16/2021, 7:06 PMproud-spoon-58287
05/17/2021, 10:45 AMaws:lambda:Function (data-feed-property-data-fetcher):
error: 1 error occurred:
* error creating Lambda Function (1): InvalidParameterValueException: The provided execution role does not have permissions to call SendMessage on SQS
{
RespMetadata: {
StatusCode: 400,
RequestID: "1ca54399-576d-40bc-829a-c2c31790fd72"
},
Message_: "The provided execution role does not have permissions to call SendMessage on SQS",
Type: "User"
}
as per AWS docs, I have attached the following policy:
arn:aws:iam::aws:policy/service-role/AWSLambdaSQSQueueExecutionRole'
but I got the same error.
I am using the latest version of pulumi and aws in node.creamy-ice-56481
05/17/2021, 1:21 PMId = "/subscriptions/subid/resourceGroups/rg1/providers/Microsoft.Network/frontDoors/frontDoor1/frontendEndpoints/frontendEndpoint1",
bumpy-autumn-37588
05/17/2021, 3:43 PMpurple-train-14007
05/17/2021, 4:44 PMenough-truck-34175
05/17/2021, 6:52 PMdependsOn
behavior for Functions? For example, I would like listManagedClusterAdminCrdenetials
(Doc) to wait for the managed cluster to be created.full-dress-10026
05/17/2021, 7:08 PMpulumi.output(queueUrl).get()
? More context in thread.full-artist-27215
05/17/2021, 7:44 PMpulumi login --local
), what would be the value to use for organization
in a fully-qualified StackReference?curved-cartoon-90054
05/17/2021, 7:53 PMmany-psychiatrist-74327
05/17/2021, 8:49 PMgcloud
in the current machine (which makes sense, because I believe the kubeconfig for the clusters defers to the gcloud
command for auth). Is there a way to explicitly tell pulumi to use the same service account it used for creating the GCP resources? I tried setting GOOGLE_CREDENTIALS
but the behavior didn’t change.
Thanksambitious-father-68746
05/17/2021, 9:46 PMhundreds-traffic-617
05/17/2021, 11:00 PMaws.cloudwatch.EventTarget
type like sqsTarget
, but nothing explicitly mentioning step functionsred-football-97286
05/18/2021, 10:45 AMpulumi new <https://git-codecommit>
gives me an error: authentication required
.bland-army-56447
05/18/2021, 11:14 AMgifted-island-55702
05/18/2021, 12:24 PMnpm install
gifted-island-55702
05/18/2021, 12:28 PMwet-noon-14291
05/18/2021, 1:16 PMechoing-angle-67526
05/18/2021, 1:58 PMgorgeous-country-43026
05/18/2021, 2:09 PMService
for a Statefulset
- postgresql to be more specific. Statefulset
is created and pods appear as expected and based from logs etc everything is just fine including volume bindings etc. This is also true from Pulumi side when running pulumi up
to an empty cluster. Service
creation hangs up however and it finally gives up with the following error:
kubernetes:core/v1:Service (postgres):
error: 2 errors occurred:
* the Kubernetes API server reported that "default/postgres" failed to fully initialize or become live: 'postgres' timed out waiting to be Ready
* Service does not target any Pods. Selected Pods may not be ready, or field '.spec.selector' may not match labels on any Pods
I am however absolutely certain that yes, there are specified nodes available and also that those pods are indeed running. I've been banging my head against the wall with this problem for some time now and would appreciate ideas.
As an interesting detail if running pulumi up
again also the Statefulset
update seems to hang. I'll provide code snippets regarding this issue to a thread under this message.full-artist-27215
05/18/2021, 3:07 PM"grant-<ROLE_NAME>-permissions-on-X"
. Resources don't expose their logical name directly, but do expose them (at least in Python) with a "private" property _name
. The information seems to always be available (since Resource names are strings, and not pulumi.Output[str]
, so it seems "safe" from that perspective, at least). Will I be sent to Programmer Jail for doing this? Is there any thought to formally exposing the logical resource name as an officially blessed read-only property that we can use to generate additional names (or is there already a way to do this that I've missed)? Thanks 🙇