Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix spurious diff from timeouts. #576

Merged
merged 1 commit into from
Sep 11, 2020
Merged

Conversation

paddycarver
Copy link
Contributor

When testing and verifying that the imported state matches the applied
state, we're seeing some resources report that the number of elements in
the timeouts map don't match between the two states. Apparently, any
timeouts set in the config are added to state during import, but
aren't during a regular apply.

To avoid returning this incorrectly as a diff, we're just not going to
verify that.

When testing and verifying that the imported state matches the applied
state, we're seeing some resources report that the number of elements in
the `timeouts` map don't match between the two states. Apparently, any
timeouts set in the config are added to state during _import_, but
aren't during a regular apply.

To avoid returning this incorrectly as a diff, we're just not going to
verify that.
@paddycarver paddycarver added bug Something isn't working testing labels Sep 11, 2020
@paddycarver paddycarver requested a review from a team September 11, 2020 02:14
Copy link
Contributor

@appilon appilon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would only "backfire" if someone was doing test checks on the timeouts (why are these even in state?)

@ghost
Copy link

ghost commented Oct 12, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants