flat-animal-59128
05/16/2023, 3:18 PMgreat-sunset-355
05/16/2023, 3:38 PMfresh-spring-82225
05/17/2023, 1:29 AMaws:assumeRole
. For the most part it works, but I just ran into a situation where pulumi fails to delete a resource, seemingly because it’s trying to do so without the assumeRole
credentials.
I have the following in my stack yaml:
aws:assumeRole:
roleArn: arn:aws:iam::WORKFLOW_ACCT_ID:role/AWSControlTowerExecution
I run pulumi up
after assuming a role in the management account on the cli. I have a log statement in my pulumi program that shows that assumeRole
is in effect and the caller id is for the workflow acount. But it fails to delete a resource, saying the management account id isn’t allowed:
Diagnostics:
aws:ecr:LifecyclePolicy (axial-stream-repo):
error: 1 error occurred:
* AWS Account ID not allowed: MGT_ACCT_ID
pulumi:pulumi:Stack (axial-stream-dev):
current caller identity: arn:aws:sts::WORKFLOW_ACCT_ID:assumed-role/AWSControlTowerExecution/aws-go-sdk-1684286516770199000
IMAGE_TAG: latest
error: update failed
abundant-easter-70390
05/17/2023, 6:13 PMerror: anonymous.pp:31,22-32,14: cannot assign expression of type (null) to location of type list( { onDeregistration: output(string) | string, onUnhealthy: output(string) | string }
| output({ onDeregistration: string, onUnhealthy: string }))
| output(list({ onDeregistration: string, onUnhealthy: string }))?: ;
Running command as
pulumi import aws:alb/targetGroup:TargetGroup <name> <arn>
dazzling-intern-4212
05/18/2023, 4:12 AMpolite-ocean-13631
05/18/2023, 2:28 PMproud-noon-87466
05/18/2023, 4:27 PMaws:eks:NodeGroup eks-[cluster]-index-spots-mz-0 created (119s)
pulumi:pulumi:Stack aws-[cluster]-us-west-2 **failed** 5 errors
eks:index:ManagedNodeGroup eks-[cluster]-index-spots-mz-0
Diagnostics:
pulumi:pulumi:Stack (aws-[cluster]):
error: Program failed with an unhandled exception:
Traceback (most recent call last):
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/resource.py", line 602, in do_rpc_call
return monitor.RegisterResource(req)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/grpc/_channel.py", line 1030, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/grpc/_channel.py", line 910, in _end_unary_response_blocking
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "Cannot read properties of undefined (reading 'map')"
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"Cannot read properties of undefined (reading \'map\')", grpc_status:2, created_time:"2023-05-18T00:39:30.364908383+00:00"}"
>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/runner/actions-runner/_work/_tool/pulumi/3.60.0/x64/pulumi-language-python-exec", line 197, in <module>
loop.run_until_complete(coro)
File "/home/runner/actions-runner/_work/_tool/Python/3.7.12/x64/lib/python3.7/asyncio/base_events.py", line 587, in run_until_complete
return future.result()
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 126, in run_in_stack
await run_pulumi_func(lambda: Stack(func))
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 51, in run_pulumi_func
await wait_for_rpcs()
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 110, in wait_for_rpcs
raise exception
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/rpc_manager.py", line 68, in rpc_wrapper
result = await rpc
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/output.py", line 98, in is_value_known
return await is_known and not contains_unknowns(await future)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/output.py", line 98, in is_value_known
return await is_known and not contains_unknowns(await future)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/output.py", line 98, in is_value_known
return await is_known and not contains_unknowns(await future)
[Previous line repeated 19 more times]
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/resource.py", line 607, in do_register
resp = await asyncio.get_event_loop().run_in_executor(None, do_rpc_call)
File "/home/runner/actions-runner/_work/_tool/Python/3.7.12/x64/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/resource.py", line 604, in do_rpc_call
handle_grpc_error(exn)
File "/home/runner/actions-runner/_work/iac/iac/pulumi/aws/venv/lib/python3.7/site-packages/pulumi/runtime/settings.py", line 276, in handle_grpc_error
raise grpc_error_to_exception(exn)
Exception: Cannot read properties of undefined (reading 'map')
error: TypeError: Cannot read properties of undefined (reading 'map')
at /snapshot/eks/bin/nodegroup.js:894:32
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:257:35
at Generator.next (<anonymous>)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:236:12)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:190:65
at processTicksAndRejections (node:internal/process/task_queues:95:5)
error: TypeError: Cannot read properties of undefined (reading 'map')
at /snapshot/eks/bin/nodegroup.js:894:32
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:257:35
at Generator.next (<anonymous>)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:236:12)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:190:65
at processTicksAndRejections (node:internal/process/task_queues:95:5)
error: TypeError: Cannot read properties of undefined (reading 'map')
at /snapshot/eks/bin/nodegroup.js:894:32
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:257:35
at Generator.next (<anonymous>)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:236:12)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:190:65
at processTicksAndRejections (node:internal/process/task_queues:95:5)
error: TypeError: Cannot read properties of undefined (reading 'map')
at /snapshot/eks/bin/nodegroup.js:894:32
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:257:35
at Generator.next (<anonymous>)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:21:71
at new Promise (<anonymous>)
at __awaiter (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:17:12)
at applyHelperAsync (/snapshot/eks/node_modules/@pulumi/pulumi/output.js:236:12)
at /snapshot/eks/node_modules/@pulumi/pulumi/output.js:190:65
at processTicksAndRejections (node:internal/process/task_queues:95:5)
abundant-notebook-81469
05/20/2023, 12:04 AMairflow db upgrade
, but I need to run this command once some scripts stopped running inside the ECS containers, so this I have to watch for this containers to be ready after being replaced, and then run the command.
What's the best strategy in this case to run a script inside a container after a task definition in ECS and it's container/task is replaced AND a process inside it's container already finished?delightful-camera-97029
05/22/2023, 6:29 AMDiagnostics:
aws:lambda:ProvisionedConcurrencyConfig (lambda-provisioned-concurrency):
error: 1 error occurred:
* updating urn:pulumi:dev::lambda::aws:lambda/provisionedConcurrencyConfig:ProvisionedConcurrencyConfig::lambda-provisioned-concurrency: 1 error occurred:
* updating Lambda Provisioned Concurrency Config (lambda-handler-dev:live): InvalidParameterValueException: Alias with weights can not be used with Provisioned Concurrency
{
RespMetadata: {
StatusCode: 400,
RequestID: "69dfe9f6-7991-4f9e-8ce1-aae34e8ba629"
},
Message_: "Alias with weights can not be used with Provisioned Concurrency",
Type: "User"
}
pulumi:pulumi:Stack (lambda-dev):
error: update failed
although if given sometime, when I check at the console, the update actually went tru.clean-window-19746
05/22/2023, 10:32 PMundefined variable
error when the import is trying to generate the code.great-sunset-355
05/23/2023, 7:44 AMsome-nail-32772
05/23/2023, 2:32 PMFailed to modify Neptune Cluster (xxxxxx): InvalidParameterCombination: The current DB instance parameter group xxxxinstanceparametergroupxxxxx is custom. You must explicitly specify a new DB instance parameter group, either default or custom, for the engine version upgrade.
status code: 400, request id: ba8c9fb9-a3bc-43a5-bca9-20324bca10c3
I specified the parameter group explicitly, so I don’t understand what I am missing
What am I doing wrong?
Thanksdry-journalist-60579
05/24/2023, 1:55 AMbright-orange-69401
05/24/2023, 11:13 AMapigatewayv2.Authorizer
which is used in an apigatewayv2.Route
, but when I delete the stack it wants to delete the Authorizer first (which makes sense), and I get this error:
* deleting API Gateway v2 authorizer: ConflictException: Cannot delete authorizer 'authorizer-bar', is referenced in route: $connect
So basically I’m kinda stuck with this loop : Authorizer -> Route -> Authorizer
(Even though it technically depends on the Authorizer in order to be created, I need to delete the Route before deleting the Authorizer)few-pillow-1133
05/24/2023, 11:20 AMfailed to discover plugin requirements: calling `python -m pip list -v --format json`: exit status 1
proud-pizza-80589
05/24/2023, 3:37 PMflaky-finland-22550
05/25/2023, 11:47 AMbetter-translator-47169
05/26/2023, 1:50 AMabundant-easter-70390
05/26/2023, 7:26 AMaws:rds:Instance (<name>):
warning: One or more imported inputs failed to validate. This is almost certainly a bug in the `aws` provider. The import will still proceed, but you will need to edit the generated code after copying it into your program.
warning: aws:rds/instance:Instance resource '<name>' has a problem: Conflicting configuration arguments: "db_name": conflicts with name. Examine values at 'Instance.DbName'.
warning: aws:rds/instance:Instance resource '<name>' has a problem: Conflicting configuration arguments: "name": conflicts with db_name. Examine values at 'Instance.Name'.
on importing an RDS instance, any ideas?gorgeous-lunch-7514
05/26/2023, 11:29 AMaws:profile
to our test sub aws account. If I deploy w/o the profile to the creds within env vars it works but I’m getting authorisation failed from k8s errors within the GitHub action I’m running, the other AWS specific stacks are deploying correctly but stops at k8s.
Any advice?
I’m seeing this a lot within github issues but not really a suitable solution.
Errors within thread.rich-motorcycle-71684
05/29/2023, 7:56 AMproperties:
forceDelete: true
but the https://www.pulumi.com/registry/packages/awsx/api-docs/ecr/repository/#repository_yaml doesn't have this input property...strong-helmet-83704
05/29/2023, 9:57 PMflaky-finland-22550
05/30/2023, 7:46 AMable-flag-79751
05/30/2023, 12:58 PMpulumi destroy -s <my-stack>
), I can’t get them destroyed as it can’t successfully delete those resources that I’ve manually deleted on the aws console. I also tried to delete the stack entirely (pulumi stack rm <my-stack>
), and it’s the same error I’m getting. Please see image below for more info:rough-jewelry-40643
05/30/2023, 4:32 PMup
on a stack with a cloudfront distribution pulumi want to updtate the egag & lastModifiedTime. I can't find a way to ignore this. Am I missing something?
Here is a screen shot of the issue I am trying to resovle/ignorebreezy-morning-56714
05/30/2023, 10:03 PMenvironmentFiles: [{
value: "some arn value",
type: "?? what goes here",
}]
breezy-morning-56714
05/30/2023, 10:24 PMable-flag-79751
05/31/2023, 11:37 AMflaky-finland-22550
06/01/2023, 10:35 AMcalm-queen-58154
06/01/2023, 2:56 PMCalling __str__ on an Output[T] is not supported.
To get the value of an Output[T] as an Output[str] consider:
1. o.apply(lambda v: f"prefix{v}suffix")
See <https://pulumi.io/help/outputs> for more details.
This function may throw in a future version of Pulumi.
Ref stack does a bucketV2
pulumi.export("bucket", bucket.id)
With the following used in the stack using it
bucket = core_stack_ref.get_output("bucket")
It does not want to work and I cannot help but feel I'm missing something. ANy idea?