-
Notifications
You must be signed in to change notification settings - Fork 72
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
Terraform Provider Development Program - Second Review #66
Comments
#47 |
for the first one , get in touch with our PM |
Will infobloxopen/terraform-provider-infoblox be published to the Terraform Registry? Providers can be published here: https://registry.terraform.io/publish/provider Update (July 2021): The verified Infoblox Terraform provider is now available in the Terraform Registry: https://registry.terraform.io/providers/infobloxopen/infoblox/latest |
@mocofound yep will be doing that |
Curious if there have been any updates regarding the provider review? Keen to use this soon! |
I'm probably make some noise, but is there any ETA for publishing this provider in the registry ? |
@cgriggs01 how can we help on this ? |
"Presently we are working on couple of enhancements. Once we are done with them we would be looking to publish it under verified provider. We will be soon reaching out." |
Can we support you on this? It would be nice if we could get in the near future a published version on the terraform registry. |
With the new provider Registry the publishing process is self service and con be done once the a release has been built using Github actions. This issue and feedback was from our old process of onboarding providers into the native ecosystem. |
This was closed, but I don't see this provider in the official registry. Have you published this yet? |
Not yet. We have a similar issue at https://github.com/infobloxopen/terraform-provider-infoblox/issues/67. You can track it for updates. |
The verified Infoblox Terraform provider is now available in the Terraform Registry: https://registry.terraform.io/providers/infobloxopen/infoblox/latest |
Hey Team, I took another review pass at this repository and here is my current feedback:
I have haven’t attempted to create an Infoblox support account, but I’m not sure my submission has gone through. Could you provide an organization_id so that I can get access to the Infoblox binary.
The provider must have documentation built for the provider its resources and data sources as well and guide that can help users that will be posted to terraform.io. All for the official Terraform providers follow the same format for the website docs.
make website
to deploy your website docs locally.The GNUmakefile should align with the standard makefile, you should copy of the Github GNUmakefileand you’l just need to change line Wapi Validate Function and Gateway ip address #4
PKG_NAME=infoblox
All official Terraform provider use a Mozilla Public License 2.0 within each repo, can you change from the Apache license to a MPL2.0 LICENSE file in this repository.
The CHANGELOG formatting will have to be updated to conform to the standard provider format since the changeling is updated by a bot during the release it must be in a certain format. With the AWS provider changelog as an example, the version of the next release should be tagged as “1.0.0 (Unreleased)” and will then be updated with a date by the release-bot.
One of our Terraform Ecosystem engineers built a linter to help align coding best practices for providers. You should use it along with your development moving forward. https://github.com/bflad/tfproviderlint. There is only one test failing right now with is
AT003
but that should not be a require and you can disregard it.Each Terraform provider requires a .travis.yml which is use to just run the unit test to verify that the provider builds successfully as a PR check in the repo.
The text was updated successfully, but these errors were encountered: