Skip to content

How to handle drift in auto-scaling groups? #7

@catherinevee

Description

@catherinevee

I'm using DriftMgr to detect drift in our AWS infrastructure, but I'm getting false positives for auto-scaling groups where instance counts change frequently. Is there a way to ignore certain attributes or resource types?

Current command:

driftmgr drift detect --state s3://my-bucket/terraform.tfstate --provider aws

Would appreciate guidance on best practices for dynamic resources.

Metadata

Metadata

Assignees

No one assigned

    Labels

    provider: awsAWS provider relatedquestionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions