feat: diff changelog for mongodb #11269
Conversation
Signed-off-by: Animesh Pathak <[email protected]>
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://689de6057a50522f4eb92cad--harness-developer.netlify.app |
| @@ -0,0 +1,169 @@ | |||
| --- | |||
There was a problem hiding this comment.
this feels like a weird place to put this file in our navigational hierarchy. Why are we putting it here instead of under 'build-a-changelog? why isn't 'build-a-changelog' linking to it?
| By automating this process in a Harness pipeline, you can: | ||
| - Avoid manual changelog creation for legacy or existing databases | ||
| - Standardize schema tracking using Liquibase-compatible formats (JSON or YAML) | ||
| - Keep your database changes **fully GitOps-compliant** with version control and peer review |
There was a problem hiding this comment.
this article barely talks about gitops, so I would personally remove this bullet and pull this out of the gitopos section..... there isn't anything mongodb specific about how we do gitops....
| - Validate changelog generation in a staging pipeline before committing to production branches | ||
| - Parameterize connection details using Harness pipeline variables | ||
| - Always use a read-only MongoDB user for schema extraction | ||
| By integrating this process into Harness pipelines, you ensure repeatable, auditable, and version-controlled database schema onboarding—a cornerstone of GitOps-driven database delivery. |
There was a problem hiding this comment.
this article barely talks about gitops, so I would personally remove this bullet and pull this out of the gitopos section..... there isn't anything mongodb specific about how we do gitops....
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: