-
Notifications
You must be signed in to change notification settings - Fork 112
feat: add PRODUCT_CONFIG #87
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
Conversation
Vercel Previews Deployed
|
EnMod
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.
Deferring to @RubenSandwich for a final sign-off, but LGTM!
RubenSandwich
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.
Overall looks good. Let's just add a key to repoConfig "unversionedDoc: boolean" or "versionedDoc: boolean" you choice, as I believe that will help clean up certain parts of our code.
If you feel that that work would be better in a PR, as this PR already contains a lot of changes, then I will approve this and we can make a new ticket for that work.
RubenSandwich
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.
Looks great. 👍🏻
* WIP * feat: add PRODUCT_CONFIG * remove comment and add types to PRODUCT_CONFIG * remove console log * fix attribute name * add attribute comment * remove unnecessary comment * add versionedDocs to product config
Description
🎟️ Asana task
This PR creates a PRODUCT_CONFIG object that can be used across the repo to access any product config information. This mainly gets used in the migration scripts but also is used across a few other scripts in the repo. I also added the
productSlugattribute to contain the product name that the repo belongs to. For example, terraform-docs-agents content shows up in the terraform section of dev-portal so theproductSlugfor that section is 'terraform'.Testing
.content-source-reposdirectory is created and contains docs repos