No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

can someone help me with the `ignoreChanges` path - if there is documentation on this somewhere I’m having trouble finding it, this is the best I’ve found so far: <https://github.com/pulumi/pulumi/pull/3005/files/8a4b20b05ec9c4ceb1535d90ddb350319655a8c3#diff-7bb15b0066584f354ca6a55865d99ffeR29>

my code, I’d like to not update the index writeCapacity if it’s been adjusted by autoscaling

```// groups
var regional_groups_table_name = `${company}-${env}-groups`;
var regional_groups_table = new aws.dynamodb.Table(regional_groups_table_name, {
    name: regional_groups_table_name,
    hashKey: 'id',
    streamEnabled: true,
    streamViewType: 'NEW_AND_OLD_IMAGES',
    readCapacity: 1,
    writeCapacity: 1,
    attributes:[{
        name: 'id',
        type: 'S'
    },{
        name: 'name',
        type: 'S'
    }],
    globalSecondaryIndexes:[{
        name: `${regional_groups_table_name}-gsi-name`,
        hashKey: 'name',
        projectionType: 'KEYS_ONLY',
        readCapacity: 1,
        writeCapacity: 1
    }]
},{
    ignoreChanges: [
        '.writeCapacity',
        '.globalSecondaryIndexes.writeCapacity'
    ]
});```

doesn’t seem to be working, however, it’s attempting to adjust the capacity which has been autoscaled up to 10

ah, k looks like this works: ```    ignoreChanges: [
        '.writeCapacity',
        '.globalSecondaryIndexes[0].writeCapacity',
        '.globalSecondaryIndexes[1].writeCapacity'
    ]```

appears I have to do one for each though, haven’t been able to wildcard or apply to all