steep-beach-52652
11/10/2021, 4:25 PMsteep-beach-52652
11/10/2021, 4:39 PMsteep-beach-52652
11/10/2021, 4:39 PM"managedAgents": [
{
"lastStartedAt": "2021-11-10T14:35:43.210000+00:00",
"name": "ExecuteCommandAgent",
"lastStatus": "RUNNING"
}
],
"cpu": "0"
}
],
"cpu": "256",
"createdAt": "2021-11-10T14:35:03.404000+00:00",
"desiredStatus": "RUNNING",
"enableExecuteCommand": true,
steep-beach-52652
11/10/2021, 4:41 PMaws ecs execute-command --cluster cluster-79da775 --task 4791ddaf725a4244a39fcf01943a5ce7 --container my-app --interactive --command "/bin/sh"
The Session Manager plugin was installed successfully. Use the AWS CLI to start a session.
An error occurred (TargetNotConnectedException) when calling the ExecuteCommand operation: The execute command failed due to an internal error. Try again later.
magnificent-lifeguard-15082
11/11/2021, 10:34 AMaws-sdk
. For extra context, I’m not using inline functions but referencing an externally packaged zip for lambda. This can reference any required pulumi runtime but not entirely sure where to start.colossal-boots-62227
11/12/2021, 2:53 AMsteep-beach-52652
11/12/2021, 5:58 AMsteep-beach-52652
11/12/2021, 5:58 AMsteep-beach-52652
11/15/2021, 1:51 PMwonderful-twilight-70958
11/15/2021, 2:50 PMif env == dev: do x elif env == prod do y
?acceptable-insurance-51692
11/17/2021, 10:06 AMoriginal_src_path = /path/to/origObj
new_src_path = /path/to/newObjWhen I execute pulumi up and select details, I see 3 actions are about to be done:
++awss3/objectCopyObjectCopy: (create-replacement)
+-awss3/objectCopyObjectCopy: (replace)
--awss3/objectCopyObjectCopy: (delete-replaced)When I execute them, they happen in order, i.e. create, replace, delete. Thing is, the delete is deleting the newly created file (which has the same path), so I'm left with an empty bucket. To emphasize - create-replacement creates the object, but it's subsequently deleted. Question is, what am I doing wrong? Edit: apparently adding the following reverses the order of operation and works around the problem. seems like a bug to me though.
{deleteBeforeReplace: true}
lively-student-98057
11/17/2021, 10:04 PMconst publicCluster = new eks.Cluster(`eks-cluster`, {
vpcId: vpc.id,
publicSubnetIds: publicSubnetIds,
privateSubnetIds: privateSubnetIds,
nodeAssociatePublicIpAddress: false,
createOidcProvider: true,
providerCredentialOpts: {
profileName: aws.config.profile,
},
});
I can confirm that the resulting EKS cluster is properly associated with the specified subnets.
Anyone have any advice?fast-rain-29589
11/18/2021, 1:39 AMsteep-beach-52652
11/18/2021, 7:37 AMsteep-beach-52652
11/18/2021, 7:40 AMResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to get registry auth from asm: service call has been retried 5 time(s): failed to fetch secret arn:aws:secretsmanager:us-west-2:3798216913...
miniature-window-2464
11/18/2021, 1:54 PMswift-pharmacist-99893
11/19/2021, 10:41 AMpython main.py
but my tests fail with the following error Program run without the Pulumi engine available; re-run using the pulumi CLI
. Did someone know how to test inline programs?witty-honey-13693
11/20/2021, 2:09 PMsteep-sunset-89396
11/21/2021, 11:03 AMwitty-honey-13693
11/22/2021, 10:23 AMastonishing-elephant-65796
11/23/2021, 8:21 PM$ pulumi new kubernetes-typescript -v=3 --force
This command will walk you through creating a new Pulumi project.
Enter a value or leave blank to accept the (default), and press <ENTER>.
Press ^C at any time to quit.
project name: (quickstart)
project description: (A minimal Kubernetes TypeScript Pulumi program)
Created project 'quickstart'
Please enter your desired stack name.
`To create a stack in an organization, use the format <org-name>/<stack-name> (e.g. acmecorp/dev
).`
stack name: (dev)
Created stack 'dev'
Installing dependencies...
up to date, audited 123 packages in 699ms
30 packages are looking for funding
`run npm fund
for details`
found 0 vulnerabilities
Finished installing dependencies
Your new project is ready to go! :sparkles:
To perform an initial deployment, run 'pulumi up'
$ ls
Pulumi.yaml index.ts node_modules package-lock.json package.json tsconfig.json
astonishing-elephant-65796
11/23/2021, 8:21 PMsticky-country-73582
11/23/2021, 8:56 PMCluster
class in pulumi-aws v4.29.0, when trying to add
auto_termination_policy=pulumi_aws.emr.ClusterAutoTerminationPolicyArgs(
idle_timeout=<some-int-value>,
)
I get the following error -
AttributeError: module 'pulumi_aws.emr' has no attribute 'ClusterAutoTerminationPolicyArgs'
error: an unhandled error occurred: Program exited with non-zero exit code: 1
Is this the right way to use this? Also, are there any IAM related dependencies that should be taken care of?witty-honey-13693
11/24/2021, 1:04 PMwitty-honey-13693
11/25/2021, 3:07 AMbroad-answer-39628
11/25/2021, 9:32 AM"use strict";
const cloud = require("@pulumi/cloud-aws");
const server = new cloud.HttpServer("reviews-getter", () => {
const app = require('./app/app');
return app;
})
module.exports = server;
./app/app.js
is the express object exported from another file.
The problem is that after pulumi up
, index.js is successfully converted into a lambda function but the ./app folder is not included in the code. I therefore get an error saying that module ‘./app/app’ cannot be found. Moving the code in ./app/app.js into index.js does not help either because of the other dependencies in ./app which cannot be accessed.
cloud:functionIncludePaths: ./app/
is already declared in the config so could someone please advise on how to resolve this? Thanks in advance!fierce-vr-50495
11/26/2021, 3:36 PMgo run main.go
I get the following output
2021/11/26 16:28:42 Created/Selected stack "org/proj/stack"
2021/11/26 16:28:42 Installing the Kubernetes Plugin
2021/11/26 16:28:42 Successfully installed kubernetes v3.10.1
2021/11/26 16:28:44 Successfully set config
2021/11/26 16:28:44 Starting refresh
2021/11/26 16:28:45 Failed to refresh stack: failed to refresh stack: exit status 255
code: 255
stdout:
stderr: error: no stack named 'org/proj/stack' found
exit status 1
Any hints what I’m missing might miss?mammoth-engineer-60103
11/28/2021, 4:08 PMserver = aws.ec2.Instance(
"pulumi_made",
ami=ami.id,
vpc_security_group_ids=[security_group.id],
instance_type="t2.micro",
tags=common_tags,
key_name=ec2_key_name,
# availability_zone="us-east-1a",
ebs_block_devices=[aws.ec2.InstanceEbsBlockDeviceArgs(
delete_on_termination=True,
volume_size=10,
device_name="/dev/sda1"
)],
volume_tags=common_tags
)
everytime I run
pulumi up
it recreates a new instance even if the code has not changed. what am I doing wrong? i couldnt find anything in docs.mammoth-engineer-60103
11/28/2021, 4:09 PMpulumi:pulumi:Stack: (same)
[urn=urn:pulumi:dev::iac-lab2-ec2::pulumi:pulumi:Stack::iac-lab2-ec2-dev]
++aws:ec2/instance:Instance: (create-replacement)
[id=i-055c1e578277fdd23]
[urn=urn:pulumi:dev::iac-lab2-ec2::aws:ec2/instance:Instance::pulumi_made]
[provider=urn:pulumi:dev::iac-lab2-ec2::pulumi:providers:aws::default_4_29_0::7d347e6c-5fb5-4e2b-bc1f-f2e5ff067bf1]
~ ebsBlockDevices: [
~ [0]: {
~ deleteOnTermination: true => true
~ deviceName : "/dev/sda1" => "/dev/sda1"
+ volumeSize : 10
}
]
+-aws:ec2/instance:Instance: (replace)
[id=i-055c1e578277fdd23]
[urn=urn:pulumi:dev::iac-lab2-ec2::aws:ec2/instance:Instance::pulumi_made]
[provider=urn:pulumi:dev::iac-lab2-ec2::pulumi:providers:aws::default_4_29_0::7d347e6c-5fb5-4e2b-bc1f-f2e5ff067bf1]
~ ebsBlockDevices: [
~ [0]: {
~ deleteOnTermination: true => true
~ deviceName : "/dev/sda1" => "/dev/sda1"
+ volumeSize : 10
}
]
--outputs:--
~ hostname: "<http://ec2-52-90-186-159.compute-1.amazonaws.com|ec2-52-90-186-159.compute-1.amazonaws.com>" => output<string>
~ ip : "52.90.186.159" => output<string>
--aws:ec2/instance:Instance: (delete-replaced)
[id=i-055c1e578277fdd23]
[urn=urn:pulumi:dev::iac-lab2-ec2::aws:ec2/instance:Instance::pulumi_made]
[provider=urn:pulumi:dev::iac-lab2-ec2::pulumi:providers:aws::default_4_29_0::7d347e6c-5fb5-4e2b-bc1f-f2e5ff067bf1]
quick-painter-61380
11/29/2021, 6:48 PM