-
Notifications
You must be signed in to change notification settings - Fork 37
chore: remove maintainer_github from all modules and examples #231
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
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, Chris. I think it's now time to add a helper release script to make releasing easy with such a large number of module changes.
Also, can we add a linter rule to ensure there are no erroneous frontmatter entries? |
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.
Going to defer to @bcpeinhardt for final approval, since he's got a lot more context for the Registry site's build step, but I cross-referenced all the tags in the PR description with the changes in the PR, and everything looks good to me
Only thing is, I think we can actually go a bit further with our changes:
- I want to say we should be clear to remove the
partner_github
field as well, since it andmaintainer_github
were both officially deprecated, and we've switched to a different publishing system. That would affect:hcp-vault-secrets
jfrog-oauth
jfrog-token
vault-github
vault-jwt
vault-token
- All the non-Coder modules still have a
maintainer_github
field - The
MAINTAINER.md
file should be updated to remove any mention ofmaintainer_github
, and (hopefully)partner_github
, too
Yup this looks aligned with registry-servers build process 😎 I agree with all of @Parkreiner 's suggestions though. Ideally those would go on this PR too. The real source of truth for the frontmatter content can be seen here: https://github.com/coder/registry-server/blob/main/sdk/codegentypes/frontmattertypes.go |
I was ironically just thinking about how I could avoid having to tag and push all of these modules individually XD |
I totally agree with removing partner_github, I was just waiting on someone to confirm that we aren't using this on the frontend anywhere since JFrog and Hashicorp modules have this field set. |
@Parkreiner and @bcpeinhardt, we might need some other way to mark some modules as partner-certified in the future. There is no immidiate need but it is a valid request from Partnserhips. |
So are we wanting to push this without the removals of I was holding on this till I had a answer on it. |
@matifali ant thoughts on this or should this be good to go in its current form? I was waiting on confirmation that removing partner_github from Jfrog or HCP to make sure it nothing is using it currently |
Let's remove this too @DevelopmentCats |
I'll get this done today and merged |
This PR updates all modules to remove maintainer_github field from frontmatter.
I also updated a few modules to 1.0.31 to be later than the latest general release on coder/modules.
All of these modules have not been tagged since the move from coder/modules. I believe they all need to move to 1.0.31 to outpace the latest published general version from coder/modules.
Modules Updated: