thankful-coat-47937
10/21/2022, 4:44 PMerror: Error serializing function 'checkForReports': lambda.ts(48,24)
function 'checkForReports': lambda.ts(48,24): referenced
'(env, project) => __awaiter(void 0, ...': configs.js(409,24): which referenced
function 'Config': configs.js(46,15): which referenced
function 'getNewGasPrice': configs.js(131,18): which captured
module './../../packages/contracts-api/dist/src/utils/logger.js' which indirectly referenced
function '<anonymous>': create-logger.js(71,46): which captured
variable 'logger' which indirectly referenced
function 'value': buffer_list.js(199,25): which referenced
function 'inspect': which captured
'ObjectKeys', a function defined at
function 'keys': which could not be serialized because
it was a native code function.
Function code:
function keys() { [native code] }
Capturing modules can sometimes cause problems.
Consider using import('./../../packages/contracts-api/dist/src/utils/logger.js') or require('./../../packages/contracts-api/dist/src/utils/logger.js') inside function 'getNewGasPrice': configs.js(131,18)
is there anything we can do to get this working without switching to the zip?prehistoric-knife-34704
10/21/2022, 10:08 PMopt
. Is that something the device_name
argument can do?lemon-intern-77136
10/21/2022, 10:56 PMpulumi up
print out secrets when it prints the describe? I’m doing some modifications of a secret variable and I can’t debug it because I can’t see the output.prehistoric-waitress-34998
10/22/2022, 8:49 AMdev
and prod
but may add more later (test, staging etc). I’m likely to follow this kind of structure for the microservices.
It feels like my options are:
1. Create an infra
folder in each application repo, and manage them as separate entities, but not sure about how to manage shared resources like networking.
2. Create an infrastructure
repo, and work out how to cross reference the resources in the build & deploy steps in my application repos.
3. Create a monorepo with all the applications in folders, and an infra
folder to handle the build & deploy
4. Something else I’m missing? 🙂
Can anyone point me to some useful resources on this? Or nudge me in the right direction? Cheersgifted-pizza-8238
10/23/2022, 9:28 AMalert-midnight-11504
10/23/2022, 9:27 PMicy-controller-6092
10/24/2022, 3:19 AMnew AssetArchive({ 'inner.zip': new FileArchive('dist/folder') })
this should produce a top-level zip, with another zip inside of it… but when I check the zip file uploaded to S3, inner.zip
is a directory not a zip archivepowerful-noon-84115
10/24/2022, 7:38 AMmake tfgen
, the provider/cmd/pulumi-resource-tencentcloud/schema.json
is generated as expected, but in the nodejs
language examples, I noticed the description
field, the import statement imports is:
```typescript
import * as pulumi from "@pulumi/pulumi";
// Unexpeceted package name, expect `@tencentcloud_iac/pulumi` which I defined in resource `PackageName`
import * as tencentcloud from "@pulumi/tencentcloud";
```
careful-hairdresser-51000
10/24/2022, 2:25 PMpulumi up
process even though I’ve deleted all references to it in the state file and imported it. I thought that the state file and the resources in the provider was a complete view of the state. Is there a cache somewhere? Does anyone know what could cause this?salmon-hairdresser-65532
10/24/2022, 2:30 PMripe-park-70944
10/24/2022, 5:13 PMlate-lock-17022
10/24/2022, 6:18 PMcolossal-room-15708
10/24/2022, 11:24 PMbut the Pulumi backend documentation explains that only Pulumi Service supports transactional checkpointing (for fault tolerance and recovery), concurrent state locking (to prevent corrupting your infrastructure state in a team environment), and encrypted state in transit and at rest. In my opinion, without these features, it’s not practical to use Pulumi in any sort of production environment (i.e., with more than one developer), so if you’re going to use Pulumi, you more or less have to pay for Pulumi Service.https://blog.gruntwork.io/why-we-use-terraform-and-not-chef-puppet-ansible-saltstack-or-cloudformation-7989dad2865c Is this all still accurate?
breezy-butcher-78604
10/25/2022, 4:32 AMpulumi up
. any ideas?flaky-arm-38472
10/25/2022, 9:58 AMfancy-xylophone-7581
10/25/2022, 12:54 PMred-scooter-62880
10/25/2022, 12:57 PMripe-park-70944
10/25/2022, 1:04 PMagreeable-whale-35898
10/25/2022, 2:22 PMDistribution
with I need to authenticate its calls with Lambda@Edge (I believe this is how it is called, anyway..). But Lambda@Edge must be located at us-east-1
, while my entire stack is at eu-central-1
. So how do I set the region of a Pulumi.Aws.Lambda.Function
?white-rain-67342
10/25/2022, 5:51 PMpostgresql:index:Grant (dev-kable_api_app-grant):
error: deleting urn:pulumi:dev::kable-infrastructure::custom:resource:DB$postgresql:index/grant:Grant::dev-kable_api_app-grant: 1 error occurred:
* error detecting capabilities: error PostgreSQL version: dial tcp: lookup <http://dev-db-rds0775ab0.ce3zgd4y8bpu.us-east-1.rds.amazonaws.com|dev-db-rds0775ab0.ce3zgd4y8bpu.us-east-1.rds.amazonaws.com> on 192.168.0.1:53: no such host
When I run refresh I get:
postgresql:index:Database (dev-kable_api-database):
error: Preview failed: refreshing urn:pulumi:dev::kable-infrastructure::custom:resource:DB$postgresql:index/database:Database::dev-kable_api-database: 1 error occurred:
* error detecting capabilities: error PostgreSQL version: dial tcp: lookup <http://dev-db-rds0775ab0.ce3zgd4y8bpu.us-east-1.rds.amazonaws.com|dev-db-rds0775ab0.ce3zgd4y8bpu.us-east-1.rds.amazonaws.com> on 205.171.2.25:53: no such host
Is there a way to run a destroy while ignoring failed deletes?cuddly-magician-97620
10/25/2022, 7:59 PM"@pulumi/aws": "^4.0.0",
"@pulumi/awsx": "^0.30.0",
to
"@pulumi/aws": "^5.0.0",
"@pulumi/awsx": "^0.40.0",
Shortly after that, I have noticed a skipDestroy
key being added to the ECS task definition outputs. I do not define this parameter anywhere in the code, it is added implicitly by Pulumi (or an upstream provider). Downgrading to the old aws/awsx packages does not help (the upstream provider is likely not downgraded with them).
The key is not recognized by aws-actions/amazon-ecs-deploy-task-definition
GitHub action and makes it fail:
Error: Failed to register task definition in ECS: Unexpected key 'skipDestroy' found in params
Error: Unexpected key 'skipDestroy' found in params
Has anyone seen this issue and/or can help?fierce-ability-58936
10/25/2022, 8:45 PMpulumi refresh --import-pending-creates
magic but it didn't work out (and frankly it looks like it's meant to be something else?).
Ideally, there should be something like "pulumi up --import target"wooden-tailor-35438
10/25/2022, 11:48 PMdatabricks_group_member
for assigning users to groups... however, that resource doesn't exist (however, that is the exact resource used in terraform 🤔) and there actually is no resource for assigning users to group... which basically defeats the point of even managing users in pulumi https://www.pulumi.com/registry/packages/databricks/api-docs/user/thousands-pizza-93362
10/25/2022, 11:49 PMthousands-pizza-93362
10/25/2022, 11:49 PMastonishing-monitor-79630
10/26/2022, 6:17 AMimport pulumi_snowflake as snowflake
class Snowflake(ComponentResource):
# Select privilege
snowflake.TableGrant(
f"{schema_name}_SCHEMA_TABLE_SELECT_GRANT",
schema_name=schema_name,
roles=all_roles,
privilege="SELECT",
on_future=True,
database_name=database
)
# Update privilege
snowflake.TableGrant(
f"{schema_name}_SCHEMA_TABLE_UPDATE_GRANT",
schema_name=schema_name,
roles=read_write_role_names,
privilege="UPDATE",
on_future=True,
database_name=database
)
However, this poses a problem the future grants will only apply to objects (i.e. tables, views etc.) created after the deployment of the new infra, while existing schema-level objects are not affected. I am thinking the best approach would be to run SQL code like:
import snowflake.connector as sfc
sf_conn = sfc.connect()
with sf_conn.cursor() as cursor:
for role in all_roles:
cursor.execute(f"grant select on all tables in {schema} to role {role})
Would it be possible to configure such “manual” “post-hooks” to be run on each pulumi up
call?famous-receptionist-48776
10/26/2022, 7:38 AMaws:eks:NodeGroup (default):
error: 1 error occurred:
* error creating EKS Node Group (dev-cnn1:default20221014114406636600000007): InvalidParameterException: Following required service principals [[<http://ec2.amazonaws.com.cn|ec2.amazonaws.com.cn> ](<https://console.amazonaws.cn/support/ec2.amazonaws.com.cn)>] were not found in the trusionships of nodeRole arn:aws-cn:iam::888888888888:role/dev-cnn1-instanceRole-role-963e580
{
RespMetadata: {
StatusCode: 400,
RequestID: "c8d401ae-bc7c-4039-9115-65d848c595d9"
},
ClusterName: "dev-cnn1",
Message_: "Following required service principals [[<http://ec2.amazonaws.com.cn|ec2.amazonaws.com.cn> ](<https://console.amazonaws.cn/support/ec2.amazonaws.com.cn)>] were not found in the trust relationships of nodeRole arn:aws-cn:iam::888888888888:role/dev-cnn1-instanceRole-role-963e580
NodegroupName: "default20221014114406636600000007"
}
Will you please help to reveiw my PR to fix this ?
https://github.com/pulumi/pulumi-eks/pull/801fancy-xylophone-7581
10/26/2022, 1:01 PMhelpful-memory-76476
10/26/2022, 1:22 PMsalmon-hairdresser-65532
10/26/2022, 1:34 PMalb.createListener("web-listener", port="80)
does not work in Python. How would the example look using Python?
I also tried something like
alb = awsx.lb.ApplicationLoadBalancer("loadBalancer",
name="internet-facing-alb",
security_groups=[security_group_loadbalancer]
listeners=[awsx.lb.ListenerArgs(port="80")]
)
but somehow it seems to me that the Input "listeners" is not known (at least I get
listeners=[awsx.lb.ListenerArgs(port="80")]
^
SyntaxError: invalid syntax
as an error. I'm using version 1.0.0b11 of awsx.salmon-hairdresser-65532
10/26/2022, 1:34 PMalb.createListener("web-listener", port="80)
does not work in Python. How would the example look using Python?
I also tried something like
alb = awsx.lb.ApplicationLoadBalancer("loadBalancer",
name="internet-facing-alb",
security_groups=[security_group_loadbalancer]
listeners=[awsx.lb.ListenerArgs(port="80")]
)
but somehow it seems to me that the Input "listeners" is not known (at least I get
listeners=[awsx.lb.ListenerArgs(port="80")]
^
SyntaxError: invalid syntax
as an error. I'm using version 1.0.0b11 of awsx.