millions-account-72180
06/13/2022, 1:54 PMwonderful-painting-69130
06/13/2022, 2:51 PMable-train-72108
06/13/2022, 3:27 PMquiet-wolf-18467
high-kilobyte-58002
06/13/2022, 4:10 PMeager-lawyer-9843
06/13/2022, 4:43 PMpulumi up
not being able to find the AWS credentials
Error: invocation of awsec2/getVpcgetVpc returned an error: unable to validate AWS AccessKeyID and/or SecretAccessKey - see https://pulumi.io/install/aws.html for details on configurationI have a profile setup in my aws credentials file and I can view the config when using the CLI but cannot get it to work with the pulumi. I had it working before but for some reason it has stopped working and I cannot find any changes that would have caused it, at least through git. FYI, I am using a monorepo for all my services and using symlinks to pull in the
package.json
and node_modules
(though even removing that has not helped). My Pulumi.stack.yaml
in each service directory has the aws:profile
and aws:region
setmany-spring-73557
06/13/2022, 7:14 PMfamous-salesclerk-74711
06/13/2022, 10:38 PMPulumi.<base>.yaml
- has the defaults
• Pulumi.<a>.yaml
- has the a
stack’s configs, as overrides from what is specified in base
• Pulumi.<b>.yaml
- has the b
stack’s configs … etc.blue-judge-71382
06/13/2022, 11:48 PM+ pulumi:pulumi:Stack Galaxy-AWS_ECS-96471806 **creating failed** 1 error
Diagnostics:
aws:iam:RolePolicyAttachment (task-definition-1142-execution-9a42f520):
error: 1 error occurred:
* creating urn:pulumi:AWS_ECS-96471806::Galaxy::awsx:ecs:FargateTaskDefinition$aws:iam/rolePolicyAttachment:RolePolicyAttachment::task-definition-1142-execution-9a42f520: 1 error occurred:
* error reading IAM Role Managed Policy Attachment (task-definition-1142-execution-189233a:arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy): couldn't find resource
pulumi:pulumi:Stack (Galaxy-AWS_ECS-96471806):
error: update failed
Even though I provide the ResouceOptions.transformations like lblackstone said:
{
transformations: [
// Update all RolePolicyAttachment resources to use aws-cn ARNs.
args => {
if (
args.type ===
'aws:iam/rolePolicyAttachment:RolePolicyAttachment'
) {
const arn: string | undefined = args.props['policyArn'];
if (arn && arn.startsWith('arn:aws:iam')) {
args.props['policyArn'] = arn.replace(
'arn:aws:iam',
'arn:aws-cn:iam'
);
}
return {
props: args.props,
opts: args.opts,
};
}
return undefined;
},
],
}
Is there anyone encounter this issue during creating AWS ECS stack in cn-northwest-1 region? Thanks!many-spring-73557
06/14/2022, 12:33 AMpulumi whoami
just shows the username. But I don’t know if I’m logged into our custom GCP state, or pulumi service.
(I can pulumi logout && pulumi login
to be safe, but I want to programmatically determine backend for scripting)blue-leather-96987
06/14/2022, 1:24 AMbreezy-laptop-42679
06/14/2022, 7:29 AMerror parsing called workflow "peopleticker/ccc/.github/workflows/pull_request.yml@master": workflow was not found.
here is the code that I am using:
name: Call a reusable workflow
permissions:
id-token: write
contents: read
on:
pull_request:
jobs:
call-workflow-passing-data:
uses: peopleticker/ccc/.github/workflows/pull_request.yml@master
cuddly-alligator-37434
06/14/2022, 9:19 AMcuddly-alligator-37434
06/14/2022, 12:55 PMambitious-father-68746
06/14/2022, 1:45 PM--target
, both pulumi pre
and pulumi up
will show only the resources that I want to update (good), but after confirming that I want to perform the update, Pulumi will try to update a resource that I haven't explicitly requested, causing failures. Has anyone seen this behaviour before?most-mouse-38002
06/14/2022, 2:08 PMbulky-agent-73210
06/14/2022, 2:14 PMpurple-plastic-64657
06/14/2022, 7:26 PMif <condition>:
my_lambda = aws.lambda_.Function(...)
When I tried this, the if statements seem to be ignored. I'm trying to create or ignore resources based on the current pulumi stackgentle-toddler-99412
06/14/2022, 10:28 PMwhite-rainbow-89327
06/15/2022, 3:30 AMatlastCidrBlock
in a managed mongodbatlas.NetworkPeering
resource using the Node version of pulumi. The option seems to have no effect and the created resource seems to always have the default value of 192.168.248.0/21
.
export const atlasPeer = new mongodbatlas.NetworkPeering('atlas-peer', {
providerName: "AWS",
awsAccountId: AWS_ACCOUNT_ID,
vpcId: VPC_ID,
projectId: ATLAS_PROJECT_ID,
containerId: mongoCluster.containerId,
accepterRegionName: AWS_REGION,
routeTableCidrBlock: '10.11.0.0/16',
atlasCidrBlock: '192.168.232.0/21',
});
This snippet creates a stack output of
{
"accepterRegionName": "us-west-2",
"atlasCidrBlock": "192.168.232.0/21",
"atlasGcpProjectId": "",
"atlasId": "XXXXXXXXXX",
"atlasVpcName": "",
"awsAccountId": "999999999",
"azureDirectoryId": "",
"azureSubscriptionId": "",
"connectionId": "pcx-XXXXXXXX",
"containerId": "XXXXXXXXXX",
"errorMessage": "",
"errorState": "",
"errorStateName": "",
"gcpProjectId": "",
"id": "XXXXXXXXX",
"networkName": "",
"peerId": "XXXXXXXXX",
"projectId": "XXXXXXXX",
"providerName": "AWS",
"resourceGroupName": "",
"routeTableCidrBlock": "10.11.0.0/16",
"status": "",
"statusName": "PENDING_ACCEPTANCE",
"urn": "urn:pulumi:staging::journey::mongodbatlas:index/networkPeering:NetworkPeering::atlas-peer",
"vnetName": "",
"vpcId": "vpc-00000000"
}
...with an atlasCidrBlock
of 192.168.232.0/21
, though the created peering connection instead has the default Atlas CIDR of 192.168.248.0/21
, as does its corresponding route table entry on my aws side.
Interestingly, the stack output's value for atlasCidrBlock doesn't even change across pulumi refresh
operations.
Is it possible I'm doing something wrong? If not, is this most likely a bug with pulumi or with atlas?
Thanks!broad-translator-40115
06/15/2022, 9:00 AMaws.lambda.CallbackFunction
.
For some reason, Pulumi started deploying these functions included a big portion of node_modules
in the package, which deploys a package size of +15.5 MB (which is too big to use as a Lambda Edge.
I have tried stripping everything in the function and making sure to prevent any open closures, basically reducing it to callback: () => {}
.
No matter what I do, it keeps including node_modules
in the lambda package itself.
It used to worked perfectly, now I have zero idea what I suddenly did wrong to trigger this.
Any ideas how I can debug this, or how I can force-exclude node_modules
from the package?astonishing-magazine-88802
06/15/2022, 11:57 AMfew-yacht-11623
06/15/2022, 2:10 PMpulumi import
. Is there any way to get pulumi to generate this code without actually importing the infra into my stack? I’d prefer to use the “`import` resource” option to manage my stack state, but I still find the code generation very helpful.purple-accountant-75904
06/15/2022, 4:48 PMpurple-accountant-75904
06/15/2022, 4:49 PMbillowy-area-48390
06/15/2022, 5:31 PMsparse-arm-65382
06/15/2022, 8:01 PMstale-orange-47562
06/15/2022, 9:29 PMquaint-pillow-20530
06/16/2022, 8:07 AMquaint-pillow-20530
06/16/2022, 8:07 AM