-
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
Add provider to terraform registry #107
Conversation
@somashekhar You are currently working on this repo, can you please look to get this provider on registry.terraform.io. |
Hi @cgroschupp our PM @saileshgiri will be working on getting this plugin on registry.terraform.io. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@skudriavtsev can you have a look.
@skudriavtsev My fork is already in the registry https://registry.terraform.io/providers/cgroschupp/infoblox/latest. I will remove it when this is done. |
@somashekhar i think we have this problem: https://github.community/t/tag-created-by-api-does-not-trigger-create/16737 https://github.community/t/github-actions-workflow-not-triggering-with-tag-push/17053 anothrNick/github-tag-action#110 It is possible to use a PAT for the workflows? |
Any idea when this is going to be published to the terraform registry? This is impacting our work. I also opened case# 00314403 with support. |
I do appreciate the community releases to the Terraform registry, but I'm also anxiously waiting for the verified Infoblox release. Will this show up as a different provider in the registry or will the current v1.1.0 provider just use the new GitHub repo? infoblox = { |
Hi @nbarsotti @LaurencelleJ, And we'll be moving to verified soon. |
Please add before merge the github secrets GPG_PRIVATE_KEY and PASSPHRASE, see more details at:
https://www.terraform.io/docs/registry/providers/publishing.html#github-actions-preferred-