building a liquibase changelog #9142
Open
+81
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jenniferopal
requested review from
stephenatwell,
HarnessTheChaos,
archit-harness and
anshul-harness
as code owners
|
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://67923c1b23163722ecb3287b--harness-developer.netlify.app |
|
|
||
| 1. Create a changelog titled `changelog.xml` **or** `changelog.yaml` in your project directory. | ||
| 2. In your changelog file, reference the directory of SQL files. Each SQL file will be treated as a | ||
| separate changeset. Here's an example of how to structure te XML changelog: |
There was a problem hiding this comment.
te should be replaced with the
| separate changeset. Here's an example of how to structure te XML changelog: | ||
|
|
||
| ```xml | ||
| <?xml version="1.0" encoding="UTF-8"?> |
There was a problem hiding this comment.
i think rather than xml we should only have examples for yaml, easier for docs and easier to maintain
| </databaseChangeLog> | ||
| ``` | ||
|
|
||
| 3. Use the command line to run Liquibase against your changelog file. |
There was a problem hiding this comment.
why we are asking customers to run liquibase outside harness?
| calculate a checksum of each change. It only executes new changesets or those with modified checksums and records successful executions in the tracking table. | ||
|
|
||
| ```xml | ||
| <changeSet id="1" author="janet"> |
There was a problem hiding this comment.
same as before, instead of xml, can it be yaml?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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: