Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
AWS CloudFormation drift detection does not support all resource types. Resources like
AWS::ElastiCache::ParameterGroupandAWS::ElastiCache::SubnetGroupreturnUNKNOWNdrift status, causingstack_master driftto exit 1 even when all supported resources are in sync. This triggers false-positive CI failures in drift detection pipelines daily.Problem
No mechanism exists to exclude specific resource types from drift failure evaluation.
Solution
Add an optional
ignore_resource_typeskey to the stack definition. When set, resources whoseresource_typematches an entry in the list are excluded before evaluating whether to callfailed. All resources are still displayed for visibility — only the failure gate is affected.Example
stack_master.yml:Checklist
🤖 Generated with Claude Code