Terraform Provider Development Program - Initial Review #70
Comments
|
Hi Chris, Thanks for your review! I have some answers to your questions and will create PRs to address the points you mention.
This depends on the credentials you used to run the tests. In our CI environment, I'm using our company's account which is paid and allows us to run the Custom Domain tests as well.
We currently use a
Will make a PR to add these scripts.
I think it might be difficult to maintain this format easily with our build bot (goreleaser). I might follow the approach done by the AWS provider to manually track the changes.
Is it important that the CI is done by TravisCI? We are more experienced using Wercker but if it's needed I can look into porting it to TravisCI.
A PR is already in to switch to MPL2.0 Cheers, |
|
Hey Alex, Thanks for the responses and questions.
The Changelog is required for the release from our side. Once the provider completes the review and testing certification we'll release the provider under the terraform-providers/ GitHub organization where our bots will help in the build and release. Best, |
|
Hi Chris, About the CustomDomain, it really depends on your Auth0 account. If the credentials you used to run the test are of a free account, the Auth0 API will respond with 403 error code as you are not allowed access to that resource: To test it locally, you must have credentials from a paid account. I have reached out to Auth0 if they could sponsor this project by means of a paid account, but the most I managed to get is a free upgrade to our companies staging account.
Okay, the change shouldn't be too disruptive so I'll rename the file.
Of course, I understand. What I mentioned is that I will opt for a manual strategy of updating the changelog in order to have more control over the formatting. Our release tool won't be able to cope with the formatting constraints. Do you have any thoughts on my question regarding TravisCI? Best, |
|
Hi @cgriggs01, I believe most of the items in your feedback have been addressed. Would you mind having another look and let me know how we can continue? With regards to the documentation, the work is under way and the skeleton is there but we haven't documented all the resources yet. We also had some trouble with the website, please see this issue. Thanks! |
|
This issue is stale because it has been open 30 days with no activity. |
|
@cgriggs01 would be nice to have another look at this. The tests now all pass since Auth0 has granted me a free open source account in which we can test custom domains properly. |
|
There is now a copied repository at terraform-providers/terraform-provider-auth0. Its also included in the official documentation. |
|
Hi @apricote. Was it not possible to fork, or transfer the repository in order to preserve issues or pull requests that are open? Also, since the release process is handled by hashicorp staff, I removed the automation I had in place to make releases. I was told I would be invited to a slack channel where I could coordinate with hashicorp on releasing. Might you be able to help me out with that? Cheers, |
|
Hi @alexkappa, I am not affiliated with Hashicorp in any way. I just found the new repository and thought that it is relevant to this ticket. You will have to ask Chris (@cgriggs01) about the slack channel and any processes. Best, |
|
My apologies, I was under the impression that you were from the hashicorp
folks.. 😅
I have sent Chris an email asking about this.
…On Wed, 19 Feb 2020 at 18:20, Julian Tölle ***@***.***> wrote:
Hi @alexkappa <https://github.com/alexkappa>,
I am not affiliated with Hashicorp in any way. I just found the new
repository and thought that it is relevant to this ticket.
You will have to ask Chris ***@***.*** <https://github.com/cgriggs01>)
about the slack channel and any processes.
Best,
Julian
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#70?email_source=notifications&email_token=AAJF677MXHMYVREMUQRWFLTRDVS5RA5CNFSM4GOSMJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIVIHQ#issuecomment-588338206>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJF677PCZOLLWLNDD6CBFLRDVS5RANCNFSM4GOSMJRQ>
.
|
|
@alexkappa Did you ever get in touch with the Hashicorp team about that cloned repo? Should we be switching over? I noticed this repo is at version v0.5.2 but the copied repo is at v0.6.0 but that copied repo doesnt have a changelog for v0.6.0, doesnt have a v0.5.2 release, and its v0.5.1 changelog doesnt match this repo's v0.5.1 changelog. |
|
I will be maintaining both for the foreseeable future so feel free to use
the one that suits you best.
I managed to get a release through Hashicorp (v0.6.0). I will be releasing
it on this repo as well but haven't gotten to it yet.
Its a process, and I will do my best to make sure that the community
doesn't suffer from the transition, but its not very easy for me as now I
have two places to deal with issues and pull requests. Please bear with me
while I figure this out.
…On Wed, 4 Mar 2020 at 20:53, Stephen ***@***.***> wrote:
@alexkappa <https://github.com/alexkappa> Did you ever get in touch with
the Hashicorp team about that cloned repo? Should we be switching over? I
noticed this repo is at version v0.5.2 but the copied repo is at v0.6.0 but
that copied repo doesnt have a changelog for v0.6.0, doesnt have a v0.5.2
release, and its v0.5.1 changelog doesnt match this repo's v0.5.1 changelog.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#70?email_source=notifications&email_token=AAJF673YBNC75SWKBHWJMKDRF2WTDA5CNFSM4GOSMJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENZ5YPI#issuecomment-594795581>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJF67YRUT2BAHLIW3AGQYTRF2WTDANCNFSM4GOSMJRQ>
.
|
|
@alexkappa Would targeting one of the two repos in question make your life easier moving forward and/or in the interim? |
|
Yes, the current repo has most of the history so its best when triaging issues. So if you can, please prefer to do so here. |
|
Hi @alexkappa I'm wondering what's the status on that one, looks like that the hashicorp repo is now archived https://github.com/terraform-providers/terraform-provider-auth0 and lot sof people will probably be stuck on 0.14 as it's the latest version published there. Anything we can do to help on that topic ? (doc ?) |
|
Hello everyone, it seems that this issue has been already solved and as such I'll be closing it down over here. In case there are new updates please feel free to reopen it. |
Hey Team, 👋 My name is Chris, I'm a member of the Partner team @ HashiCorp.
I’ve taken a look at the provider here and would like to say great work so far! I do have feedback outlined below that I’d like to see addressed before we move on to the next steps. I’m opening this issues as a sort of checklist for tracking items and discussion. The review was done on the master branch at git commit
10ab4b3All the acceptance tests are passing except for the CustomDomain test. It just appears to be failing due to that fact that this is a free tier test account. Is this the case or should all tests be passing?
Each Terraform provider must have its own terraform.io website documentation that should reside under a website/ directory. There should be a page for each resource and data source as well as an index page for the provider. Along with with must be a ruby layout file to represent the side bar directory.
There are a number of files that must be added in order for the provider to function in the Terraform native ecosystem.
You currently have a MIT License on the provider, would you be able to change that to a MPL2 which is the standard across all Terraform providers.
Let me know if you have any questions.
-Chris
The text was updated successfully, but these errors were encountered: