error: 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)

opt

device_name

pulumi up

dev

prod

infra

infrastructure

infra

new AssetArchive({ 'inner.zip': new FileArchive('dist/folder') })

inner.zip

make tfgen

provider/cmd/pulumi-resource-tencentcloud/schema.json

nodejs

description

```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"; 
```

pulumi up

but 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.

pulumi up

Distribution

us-east-1

eu-central-1

Pulumi.Aws.Lambda.Function

postgresql: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

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

"@pulumi/aws": "^4.0.0",
        "@pulumi/awsx": "^0.30.0",

"@pulumi/aws": "^5.0.0",
        "@pulumi/awsx": "^0.40.0",

skipDestroy

aws-actions/amazon-ecs-deploy-task-definition

Error: Failed to register task definition in ECS: Unexpected key 'skipDestroy' found in params
Error: Unexpected key 'skipDestroy' found in params

pulumi refresh --import-pending-creates

databricks_group_member

import 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
    )

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})

pulumi up

aws: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"
    }