straight-caravan-63576
08/30/2022, 4:04 PMsteep-toddler-94095
08/31/2022, 4:35 AMworried-balloon-88673
08/31/2022, 11:09 AMimageTag
, which specifies the tag of a container image that i'm deploying.
in my pulumi code, i'd like to read this config value to see what tag is currently deployed. is that possible?fast-island-38778
09/02/2022, 9:54 PM"dependencies": {
"@pulumi/aws": "^5.13.0",
"@pulumi/awsx": "^0.40.0",
"@pulumi/pulumi": "^3.39.1"
}
i also have attached an example error i was gettingfast-island-38778
09/02/2022, 10:55 PMcurl
the load balancer throws this error
I think my portMappings
config is correct because I expose port 8080 in my Docerfile and I specify the containerPort
to be 8080 in the portMappings
field, e.g.
const service = new awsx.ecs.FargateService("my-service", {
cluster: cluster,
taskDefinitionArgs: {
container: {
image: image,
cpu: 512,
memory: 128,
essential: true,
portMappings: [
{
containerPort: 8080,
hostPort: 8080,
},
],
},
},
});
But I noticed the application load balancer does not have any inbound rules in its security group, could this be the reason why I am getting the error?
[2/09/22 6:42] ➜ pulumi-quickstart curl <http://nginx-lb-6040493-1557012872.us-east-1.elb.amazonaws.com>
curl: (28) Failed to connect to <http://nginx-lb-6040493-1557012872.us-east-1.elb.amazonaws.com|nginx-lb-6040493-1557012872.us-east-1.elb.amazonaws.com> port 80 after 75034 ms: Operation timed out
fast-island-38778
09/02/2022, 11:47 PMgentle-zoo-32137
09/04/2022, 6:44 AMbreezy-laptop-42679
09/05/2022, 4:10 PMbrash-toothbrush-39078
09/08/2022, 12:59 AMnode_modules/@pulumi/docker.ts:115:19
.
error: Error: No 'docker' command available on PATH: Please install to use container 'build' mode.
swift-fireman-31153
09/08/2022, 6:39 PMswift-fireman-31153
09/08/2022, 6:40 PMfreezing-artist-36980
09/11/2022, 6:42 AMconst vpcConnector = new awsc.apprunner.VpcConnector("vpc-connector", {
securityGroups: [ec2SecurityGroup.id],
subnets: [pulumi.output(vpc.getSubnetsIds)], // ERROR HERE
});
It shows 1. Type 'Output<(type: VpcSubnetType) => Promise<Output<string>[]>>[]' is not assignable to type 'Input<Input<string>[]>'.
thousands-hairdresser-72380
09/11/2022, 8:42 PMzod
in a magic function but am running into this error:
TSError: ⨯ Unable to compile TypeScript:
src/index.ts(286,14): error TS2589: Type instantiation is excessively deep and possibly infinite.
It appears to be due to the bundled typescript that comes with Pulumi being incompatible with the latest version of zod.
I’ve attempted to disable the built-in typescript runtime by adding the following to Pulumi.yaml
runtime:
name: nodejs
options:
typescript: false
But now when I run pulumi up
I get
import * as pulumi from '@pulumi/pulumi'
^^^^^^
SyntaxError: Cannot use import statement outside a module
Any ideas as to how I can get around this?
I’ve tried
1. creating a new typescript config with npx tsc --init
and that doesn’t seem to help.
2. Setting "type": "module"
in package.json
3. modifying the target
, esModuleInterop
, and a few other things.
a. (trying anything haha)
4. Searching through the Pulumi
a. Slack Logs
b. Github Issues
c. Source Code
Any help would be greatly appreciated.
Thank you!abundant-hair-53100
09/13/2022, 7:22 AMconst confirmUserIamRolePolicy = new aws.iam.Policy(
'confirm-user-signup-role-policy',
{
policy: JSON.stringify({
Version: '2012-10-17',
Statement: [
{
Effect: 'Allow',
Action: [DBAction.Put],
Resource: usersTable.arn.apply((arn) => `${arn}`),
},
],
}),
}
)
export const confirmUserIamRole = new aws.iam.Role('confirm-user-signup-role', {
assumeRolePolicy: aws.iam.assumeRolePolicyForPrincipal({
Service: '<http://lambda.amazonaws.com|lambda.amazonaws.com>',
}),
managedPolicyArns: [confirmUserIamRolePolicy.arn],
})
const confirmUserIamRolePolicyAttachment = new aws.iam.PolicyAttachment(
'confirm-user-signup-role-policy-attachment',
{
policyArn: confirmUserIamRolePolicy.arn,
roles: [confirmUserIamRole],
}
)
export const postConfirmationLambda = new aws.lambda.CallbackFunction(
'post-confirmation-signup-lambda',
{
runtime: 'nodejs14.x',
callback: confirmUserSignupHandler,
role: confirmUserIamRole,
environment: {
variables: {
USERS_TABLE: usersTable.name,
REGION: region,
},
},
}
)
quick-microphone-7801
09/14/2022, 8:18 AMcurved-eye-56312
09/14/2022, 10:58 AMPulumi.<stack_name>.yaml
file I want to declare the following object:
<stack_name>:blobContainers:
1:
name: container_name1
accessLevel: Container
2:
name: container_name2
accessLevel: Blob
3:
name: container_name3
accessLevel: Container
I understand that to retrieve this object from my configuration file I need to use the following (using Typescript):
const containers = config.requireObject("blobContainers");
However, when I try to iterate over my object and access name
for example, I am not able to due to the object's type.
What is the correct way to iterate over this object?bland-thailand-60821
09/14/2022, 7:08 PMDiagnostics:
pulumi:pulumi:Stack (metal-auto-dev):
error: Running program '/Users/dsayyed/metal-auto' failed with an unhandled exception:
TSError: ⨯ Unable to compile TypeScript:
index.ts(20,3): error TS2322: Type 'Buffer' is not assignable to type 'string | Promise<string> | OutputInstance<string> | undefined'.
Type 'Buffer' is not assignable to type 'string'.
bland-thailand-60821
09/14/2022, 7:09 PMimport * as fs from "fs";
const userData = fs.readFileSync('foo.txt','utf8');
userData: fs.readFileSync('./basenode.sh'),
big-notebook-65054
09/14/2022, 10:10 PMabundant-telephone-90024
09/15/2022, 6:34 AMmost-toothbrush-43532
09/16/2022, 3:30 AMeks.Cluster
and I have error when pulumi up
from other stack.
I configured output eks.cluster kubeconfig but it seems get previous kubeconfig output.
I tried this, but it's not worked.
PULUMI_K8S_DELETE_UNREACHABLE=true pulumi refresh
this is works.
pulumi stackoutput kubeconfig
but this is not work. (get previous kubeconfig)
const eksStack = new pulumi.StackReference('organization/eks/{stack}');
const kubeconfig = eksStack.outputs.kubeconfig;
My pulumi CLI version is v3.40.0
, and my kubernetes module version "@pulumi/kubernetes": "^3.21.2"
error message belows:
pulumi preview
Previewing update (dev)
View Live: <https://app.pulumi.com/{masked}/argocd/dev/previews/ce0cceec-7ee2-4d75-aa7b-a7f9bfc1d2f0>
Type Name Plan Info
pulumi:pulumi:Stack argocd-dev 1 error
+ └─ kubernetes:core/v1:Namespace argocd-ns create
Diagnostics:
pulumi:pulumi:Stack (argocd-dev):
error: Error: invocation of kubernetes:helm:template returned an error: failed to generate YAML for specified Helm chart: could not get server version from Kubernetes: Get "<https://8D443680F22BAD26FCEA969006E150DC.yl4.ap-northeast-2.eks.amazonaws.com/version?timeout=32s>": dial tcp: lookup <http://8D443680F22BAD26FCEA969006E150DC.yl4.ap-northeast-2.eks.amazonaws.com|8D443680F22BAD26FCEA969006E150DC.yl4.ap-northeast-2.eks.amazonaws.com> on 127.0.0.53:53: no such host
anyone have this issue?adventurous-television-3865
09/20/2022, 4:56 PMsparse-intern-71089
09/21/2022, 4:06 PMsquare-hair-965
09/21/2022, 4:06 PMpulumi.all().apply()
and you can probably see the problem I run into.
Now I could just output groups as individual constants and be done with it, which I'll likely do as I only have 4-5 autoscale groups per region, but I was wondering if anyone's ever encountered this scenario and figured out a certain code pattern to make it work?
As of right now my go-to solution is to output "none" strings when trying to output arns and ids of optional infrastructure.lemon-monkey-228
09/27/2022, 1:48 PMlemon-monkey-228
09/27/2022, 1:49 PMlemon-monkey-228
09/27/2022, 1:50 PMstocky-restaurant-98004
09/27/2022, 2:36 PMlemon-monkey-228
09/27/2022, 3:14 PMbland-thailand-60821
09/27/2022, 8:18 PMindex.ts(21,3): error TS2322: Type 'Buffer' is not assignable to type 'string | Promise<string> | OutputInstance<string> | undefined'.
Type 'Buffer' is not assignable to type 'string'.