rapid-raincoat-36492
10/08/2021, 5:13 PM@pulumi/pulumi
to use the version of ts-node
I wanted it to, 8.10.2
. I opened a ticket to move ts-node
to a peer-dependency in the node sdk so that it's easier to "bring my own" version of ts-node
that I need without needing to much around with yarn resolutions: https://github.com/pulumi/pulumi/issues/8177calm-nest-80923
10/08/2021, 8:38 PM@pulumi/pulumi
on compiled code. Oddly, a service fails without an error, though it deploys with TS enable and with the CLI …
Btw, we’re using ts-node 10.* - had fewer issues than with 8.*brave-angle-33257
10/08/2021, 8:44 PM2021-10-08T20:39:52.862Z 7244c1c2-b69c-4f06-8e15-6abfac3ad1a8 INFO pulumi:providers:aws default_4_24_0 error: no resource plugin 'aws-v4.24.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource aws v4.24.0`
miniature-nest-23801
10/09/2021, 6:48 PMquaint-electrician-41503
10/10/2021, 2:12 AMpulumi up
Enter your passphrase to unlock config/secrets
(set PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE to remember):
Previewing update (dev):
Type Name Plan Info
pulumi:pulumi:Stack quickstart-dev (node:332400) ExperimentalWarning: The http2 module is an experimental API.
Type Name Plan Info
pulumi:pulumi:Stack quickstart-dev (node:332400) ExperimentalWarning: The http2 module is an experimental API.
quaint-electrician-41503
10/10/2021, 2:12 AMproud-pizza-80589
10/10/2021, 11:26 AMquaint-electrician-41503
10/10/2021, 6:49 PMquaint-electrician-41503
10/10/2021, 6:57 PMdry-sugar-63293
10/11/2021, 7:48 AMconst authDeploymentService = new k8s.core.v1.Service(authDeploymentName,
{
metadata: {
name: "auth-svc",
labels: authDeploymentAppLabels,
namespace: namespaceName,
},
spec: {
type: "LoadBalancer",
ports: [{ port: 80, targetPort: 8080 }],
selector: authDeploymentAppLabels,
},
},
{
provider: clusterProvider,
dependsOn: [authDeployment]
}
);
const authServiceManagedCert = new gcp.compute.ManagedSslCertificate("auth-cert-001", {
name: "auth-cert-001",
project: myGcpProject.projectId,
description: "Managed SSL Certificate For auth service",
managed: {
domains: [
"<http://mydomain.com|mydomain.com>"
]
}
});
const managedCertConfigMap = new k8s.core.v1.ConfigMap("managed-certificate-config", {
data: {
"1": pulumi.interpolate`{"Key":{"Namespace":"${namespaceName}","Name":"${authServiceManagedCert.name}"},"Value":{"ExcludedFromSLO":false,"SoftDeleted":false,"SslCertificateName":"${authServiceManagedCert.id}","SslCertificateBindingReported":true,"SslCertificateCreationReported":true}}}`
},
metadata: {
name: "managed-certificate-config",
namespace: "kube-system",
}
})
const ingress = new k8s.networking.v1beta1.Ingress(authDeploymentName + "-ingress", {
metadata: {
namespace: namespaceName,
annotations: {
"<http://ingress.gcp.kubernetes.io/pre-shared-cert|ingress.gcp.kubernetes.io/pre-shared-cert>": authServiceManagedCert.name,
"<http://networking.gke.io/managed-certificates|networking.gke.io/managed-certificates>": authServiceManagedCert.name
}
},
spec: {
ingressClassName: "gce",
backend: {
serviceName: authDeploymentService.metadata.name,
servicePort: 80
},
tls: [
{
hosts: ["<http://mydomain.com|mydomain.com>"],
}
],
rules: [
{
host: "<http://mydomain.com|mydomain.com>",
http: {
paths: [
{
path: "/",
backend: {
serviceName: authDeploymentService.metadata.name,
servicePort: authDeploymentService.spec.ports[0].port,
},
}
],
},
},
]
}
},
{
provider: clusterProvider,
dependsOn: [managedCertConfigMap]
});
quaint-electrician-41503
10/11/2021, 8:09 AMquaint-electrician-41503
10/11/2021, 8:09 AMlimited-artist-95518
10/11/2021, 8:26 AM400:Invalid Name
responses when i try to create aws.appsync.Resolver
resources. Is anyone here using resolvers successfully?high-answer-18213
10/11/2021, 9:52 AMsalmon-mechanic-4571
10/11/2021, 10:45 AMbrash-vr-21201
10/11/2021, 1:56 PMrapid-raincoat-36492
10/11/2021, 2:34 PMbrave-nightfall-19158
10/11/2021, 3:05 PMswift-australia-96791
10/11/2021, 3:15 PMexport const repository= aws.ecr.Repository.get("ecr-repo", ??? )
gorgeous-keyboard-22299
10/11/2021, 3:41 PM[ { protocol: "udp", ruleNo: 171, action: "allow", cidrBlock: "0.0.0.0/0", fromPort: 53, toPort: 53 }]
. I have an NTP rule exactly like this one that gets added for UDP port 123 - why would that one be OK but no-go for 53? I noticed that the AWS console recognizes port 53 as "DNS (UDP) (53)", so is there another magic protocol I need to specify in the rules for DNS?brave-nightfall-19158
10/11/2021, 4:05 PMbrave-nightfall-19158
10/11/2021, 4:26 PMproud-pizza-80589
10/11/2021, 4:52 PMproud-pizza-80589
10/11/2021, 4:53 PMaverage-market-57523
10/11/2021, 5:04 PMaverage-market-57523
10/11/2021, 5:05 PMbulky-area-51023
10/11/2021, 5:43 PMpulumi up
in different stacks? Managed to find some open issues about enabling parallelism in automation API, wanted to make sure whether it is safe in case of CLI.worried-knife-31967
10/11/2021, 7:13 PMDependsOn = { previousItem }
but a nice way to do it.
It's also a ComponentResource that I want to run in series if that matters.
This is likely one of those "I've been looking at this for like 4 hours, and the solution is obvious" kinda situationsworried-knife-31967
10/11/2021, 7:22 PMFunctionApp lastApp = null!;
foreach (var app in apps)
{
ComponentResourceOptions options = lastApp == null ? null! : new ComponentResourceOptions {
DependsOn = {
lastApp
}
};
var cosmosDbRoles = new CosmosDbRoles($"{StackConstants.ApplicationName.ToLower()}-{app.Key}-cosmosdbroles",
new CosmosDbRoleArgs()
{
ResourceGroupName = globalResourceGroup.Name,
FunctionIdentity = app.Value.AppIdentity,
CosmosDatabaseAccountName = cosmos.CosmosDatabaseAccountName,
CosmosDatabaseAccountId = cosmos.CosmosDatabaseAccountId
}, options);
lastApp = app.Value;
}
worried-knife-31967
10/11/2021, 7:22 PMworried-knife-31967
10/11/2021, 7:22 PM