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

provider/statuscake: use default status code list when updating test #12375

Merged
merged 1 commit into from
Mar 5, 2017

Conversation

andresilva
Copy link
Contributor

@andresilva andresilva commented Mar 2, 2017

This PR fixes an issue whenever a StatusCake test is updated which would clear the list of status codes considered as errors.

According to the StatusCake API documentation (https://github.com/DreamItGetIT/statuscake/blob/master/tests.go#L93), when updating a test definition the StatusCodes definition is always updated. Since currently there's no support for setting the list of status codes in terraform this would replace the list with an empty list.

This PR fixes the issue by always providing the default list of status codes when updating a test.

@stack72
Copy link
Contributor

stack72 commented Mar 5, 2017

LGTM! Thanks for the work on this :)

@stack72 stack72 merged commit d50f2ac into hashicorp:master Mar 5, 2017
samcrang added a commit to openregister/deployment that referenced this pull request Mar 17, 2017
There is some slight ugliness to work around the new backend
configuration in 0.9.0 and the fact it doesn't support interpolations.

In the short-term this means we can upgrade to 0.9.0 and get the
[StatusCake bug fix](hashicorp/terraform#12375) we need without having to change significantly how we
use and deploy Terraform.  We should probably look at using
[Terraform State Environments](https://www.terraform.io/docs/state/environments.html)
instead.
samcrang added a commit to openregister/deployment that referenced this pull request Mar 17, 2017
There is some slight ugliness to work around the new backend
configuration in 0.9.0 and the fact it doesn't support interpolations.

In the short-term this means we can upgrade to 0.9.0 and get the
[StatusCake bug fix](hashicorp/terraform#12375) we need without having to change significantly how we
use and deploy Terraform.  We should probably look at using
[Terraform State Environments](https://www.terraform.io/docs/state/environments.html)
instead.
samcrang added a commit to openregister/deployment that referenced this pull request Mar 17, 2017
There is some slight ugliness to work around the new backend
configuration in 0.9.0 and the fact it doesn't support interpolations.

In the short-term this means we can upgrade to 0.9.0 and get the
[StatusCake bug fix](hashicorp/terraform#12375) we need without having to change significantly how we
use and deploy Terraform.  We should probably look at using
[Terraform State Environments](https://www.terraform.io/docs/state/environments.html)
instead.
samcrang added a commit to openregister/deployment that referenced this pull request Mar 17, 2017
There is some slight ugliness to work around the new backend
configuration in 0.9.0 and the fact it doesn't support interpolations.

In the short-term this means we can upgrade to 0.9.0 and get the
[StatusCake bug fix](hashicorp/terraform#12375) we need without having to change significantly how we
use and deploy Terraform.  We should probably look at using
[Terraform State Environments](https://www.terraform.io/docs/state/environments.html)
instead.
samcrang added a commit to openregister/deployment that referenced this pull request Mar 17, 2017
There is some slight ugliness to work around the new backend
configuration in 0.9.0 and the fact it doesn't support interpolations.

In the short-term this means we can upgrade to 0.9.0 and get the
[StatusCake bug fix](hashicorp/terraform#12375) we need without having to change significantly how we
use and deploy Terraform.  We should probably look at using
[Terraform State Environments](https://www.terraform.io/docs/state/environments.html) instead.
@ghost
Copy link

ghost commented Apr 16, 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 and limited conversation to collaborators Apr 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants