Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Dns record fixes + expansion #29
referenced this pull request
Feb 27, 2018
Looks good to me! Two nitpicks that are not required
Mar 2, 2018
1 check passed
This was referenced
Mar 2, 2018
Should I await until next provider release or I could get last revision and build provider on my own and use it as a custom provider?
Thanks in advance!
Hey @EpiqSty – while the fix has been merged, there has been no new release since then. Here's a list of things coming in the next release:
You are welcome to pull down the master branch of this repository and build the provider yourself! This requires Go 1.9 setup on your system, but after cloning the repository simply run
@catsby , thanks for the quick reply!
Do you know anything about release plans?
I mean for manual usage upgrading from sources is kind of OK, but as we are using terraform in CI/CD environment that will requires adjustment of Jenkins jobs in order to get custom provider on the Jenkins slaves and so on.
So, this is a question about the release date, basically ;)
If it in the near future (several weeks) we could create such records locally ( using custom provider builded from sources) and push tfstates to our terraform repo.
But if we should wait for the next release several months, probably we should choose the option of using custom providers directly on the jenkins slaves.
I do not know the release date, other than "as soon as possible". There are some other PRs and features that I believe are requested in the next release.
The release date is optimistically 0-7 days, pessimistically 2-3 weeks. I cannot promise either of those, though
@catsby I have tested creation of SRV records with latest version, build from sources, but get the same error.
Unfortunately , Cloudflare API itself has no proper documentation about fields required for creating SRV records.
Looks like I found the way how to define it:
I left "value" commented just in order to mention, that SRV definition with "value" only, ends up with error "Invalid or missing data for %s record", but the same record, defined as data structure works well.