-
Notifications
You must be signed in to change notification settings - Fork 630
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
Support 0.12 #309
Support 0.12 #309
Conversation
Using the following example setup, this branch is working as expected. provider "cloudflare" {
email = "${var.cloudflare_email}"
token = "${var.cloudflare_token}"
org_id = "${var.org_id}"
}
resource "cloudflare_record" "foobar" {
domain = "${var.cloudflare_domain}"
name = "test"
value = "example.com"
type = "CNAME"
ttl = 120
} |
This really isn't ready for review just yet but when things are in "draft", the branch isn't visible to external systems so things like CI aren't triggered. |
Terraform 0.12 requires that resource names don't start with a number (although they can still contain a number). To ensure we use a consistent supported format, I've introduced `generateRandomResourceName` which will be available to all tests for use whenever a random resource name is required. Fixes the following CI exception. ``` ------- Stdout: ------- === RUN TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy === PAUSE TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy === CONT TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy --- FAIL: TestAccCloudflareLoadBalancerPool_CreateAfterManualDestroy (0.00s) testing.go:568: Step 0 error: /opt/teamcity-agent/temp/buildTmp/tf-test154368520/main.tf:2,42-54: Invalid resource name; A name must start with a letter and may contain only letters, digits, underscores, and dashes. FAIL ```
Integration tests for CI are all green with the exception of those three flakey ones which need the sweeper (addressed in #321). |
v0.12 went live like an hour ago. go go go! 😉 Anything I can do to help? |
Release to be cut in next couple of days once the dust has settled for the Hashicorp folks. In the meantime, feel free to build against |
@jacobbednarz how i can build and use ? |
Please see the building the provider section of the README. |
1.15.0 was released today with 0.12 compatibility. |
Puts all the building blocks in place for adding 0.12 support.