| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Add support back for contact_id and mark it as deprecated
|
| |
| |
| |
| | |
This makes the contact_group change backwards compatible
|
|/
|
|
|
|
|
| |
This was making the acceptance test to fail since it was using the hardcoded contact group in the code which doesn't exist any other account except for the initial developer.
https://github.com/ndench/terraform-provider-statuscake/commit/4efdab4181cd2bfd243600def27f70f0580942a3#diff-74acd2515ee5ecd44424d7a31439989eR221
This change now explicitly prompts the user to include the contact group
|
|
|
|
|
| |
provider: Run go fix
provider: Run go fmt
|
|
|
|
| |
This allows for multiple contacts per test.
|
| |
|
|
|
|
| |
Since it was failing `make test` on travis. Must be a better way to go about this, but I couldn't come up with a better way that defaulting the value to avoid the error when running non-acceptance tests.
|
|
|
|
|
|
| |
response
The `TestCheckResourceAttr` tests can stay since they rely on the state from the previous apply.
|
|
|
|
| |
Note that we also don't check the individual locations anymore. The key numbers will be randomized and not testing content seems to be the method employed by the AWS provider as well https://github.com/terraform-providers/terraform-provider-aws/blob/81bba6b1f567aed561c6a6a30916504ee0886c68/aws/resource_aws_autoscaling_group_test.go#L404
|
|
|
|
| |
They were present in the details but the values were different during my testing. Hopefully this proves true for all future testing.
|
|
|
|
| |
In my testing, the default response was `[""]` and having the default provided cause test assertion failures
|
|
|
|
| |
Avoids showing the password in plan output
|
|
|
|
| |
This allowed me to run acceptance tests on my own account.
|
|
|
|
| |
vendor directory
|
| |
|
| |
|
|
|
|
| |
module
|
|
|