-
Notifications
You must be signed in to change notification settings - Fork 4
Rework documentation and cleanup scripts #42
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
96a50f6 to
f0a478e
Compare
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
313f118 to
a35506a
Compare
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
49e4510 to
77d6e92
Compare
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Even though GH redirects to the correct repository when cloning from the opentffoundation, that is clearly wrong and confusing. Replacing the old name of "opentffoundation" with "opentofu" Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
a12b8c8 to
e8d0520
Compare
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
yottta
left a comment
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.
Left some comments for some things that I wanted to point out in case somebody have something against or something to add.
In addition to that, please comment (or just update this branch with your own commits) with other information that you consider valuable for future usage of these scripts:
- what GPG keys are stored where? How those are generated for scripts vs terraform-provider-* repos (do all the repos have the same key? or any one of those have a different key?)
- do we have any terraform-provider-* repositories that shouldn't be managed by these scripts? (ie: lua?) If yes, why?
| ### [`gpg.yml`](./.github/workflows/gpg.yml) | ||
| This can generate new GPG keys for the provider repositories to use those for signing new releases. | ||
| > [!WARNING] | ||
| > From the looks of it, in the [gpg script](./go/gpg/main.go), the lifespan of such keys is hardcoded to 3 years. |
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.
If somebody can offer more context here on how the renewal of this should be handled, would be great to have it for the future.
lbordowitz
left a comment
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.
All the READMEs made sense and gave me a good handle on how to run them and why.
Gogotchuri
left a comment
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.
Thanks for doing this work!
Made a lot simpler to understand what each part of this repository does.
diofeher
left a comment
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.
Great stuff!
b91b6d6 to
9cda7ac
Compare
This PR tries to make clearer what scripts in this repo are for and how should be used together with the workflows.
The main points that I wanted to tackle (and it's up to the reviewer to say if it's enough or not) are as follows: