liquid-labs / liquid-labs/cloudsite
Resolve 'Internal Errors' in drift detection
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Overview
When we run `cloudsite verify`, the drift detection fails with a bunch of resources failing to detect drift based on "Internal Error"s. Some moderate googling failed to turn up anything helpful. [One post](https://repost.aws/questions/QUMDmQpSG7QQ6-kl6nInkTmQ/cloudformation-internal-failure-on-drift-detection-with-certain-resources) suggested that checking individual resources might succeed, but when we tested this (using `aws` CLI) wasn't true in our case and it failed even when just checking the individual resource.
Is this a bug on the AWS side of things?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with `cloudsite verify`, then compare it with drift checks run through the `aws` CLI for individual resources. Determine whether the internal errors are actionable in cloudsite or originate from AWS; done means a confirmed fix or a documented explanation and reproducible limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100