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 order for reading start times on downtime #145

Merged
merged 2 commits into from
Jan 16, 2019

Conversation

nmuesch
Copy link
Contributor

@nmuesch nmuesch commented Jan 16, 2019

This PR fixes the order for reading the start dates and end dates for downtimes.

Currently, if you use start_date or end_date in your configuration file, you can create the initial downtime OK. However, when you run terraform apply, Terraform will notice that the state is different than whats in the config and attempt to update it. However, since the build downtime struct saw that the start field was in the state, it used that instead of the user provided start_date. This makes sure we take precedence of the start_date field.

If the user specifies the start and end this functionality will still work as expected.

@ghost ghost added the size/XS label Jan 16, 2019
@gmmeyer gmmeyer merged commit 63ba28d into DataDog:master Jan 16, 2019
@nmuesch nmuesch deleted the nick/fix_start_time branch January 16, 2019 15:42
jbenais pushed a commit to jbenais/terraform-provider-datadog that referenced this pull request Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants