feat: add mongoDB changset example #10914
Open
+181
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
Please describe your changes:
This pull request introduces a new documentation page, "Get Started with Changelogs," to guide users on how to define and manage changelogs for SQL and MongoDB in Harness Database DevOps. The page includes detailed examples of changelogs for both database types, showcasing schema changes, indexing, and sample data management.
SQL Changelog Examples: The page provides YAML examples for SQL changelogs, demonstrating how to create tables, add indexes, insert sample data, and define rollback operations.
MongoDB Changelog Examples: Similarly, the page includes YAML examples for MongoDB changelogs, showcasing operations like creating collections, adding indexes (including unique and compound indexes), and managing context-specific changes.
Jira/GitHub Issue numbers (if any): https://harness.atlassian.net/browse/DBOPS-1327
Preview links/images (Internal contributors only): __________________
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: