How to prevent Liquibase from executing a modified version of the changelog?
I'm running Liquibase 3.6.2 and am looking for a way to prevent developers from modifying an existing changelog by adding/removing changesets. Liquibase defines a changeset as non-mutable; changing any parameter or dependency in a changeset will throw a violation error, but unfortunately, I do not see any way to prevent this from a changelog perspective.
Essentially, I'm trying to implement a convention that once a changelog is run, it can no longer be modified. New changesets must be added to a newer changelog instead.
Is there anyway I can accomplish this? How does everyone else manage non-mutability of changelogs?
liquibase
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
add a comment |
I'm running Liquibase 3.6.2 and am looking for a way to prevent developers from modifying an existing changelog by adding/removing changesets. Liquibase defines a changeset as non-mutable; changing any parameter or dependency in a changeset will throw a violation error, but unfortunately, I do not see any way to prevent this from a changelog perspective.
Essentially, I'm trying to implement a convention that once a changelog is run, it can no longer be modified. New changesets must be added to a newer changelog instead.
Is there anyway I can accomplish this? How does everyone else manage non-mutability of changelogs?
liquibase
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30
add a comment |
I'm running Liquibase 3.6.2 and am looking for a way to prevent developers from modifying an existing changelog by adding/removing changesets. Liquibase defines a changeset as non-mutable; changing any parameter or dependency in a changeset will throw a violation error, but unfortunately, I do not see any way to prevent this from a changelog perspective.
Essentially, I'm trying to implement a convention that once a changelog is run, it can no longer be modified. New changesets must be added to a newer changelog instead.
Is there anyway I can accomplish this? How does everyone else manage non-mutability of changelogs?
liquibase
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
I'm running Liquibase 3.6.2 and am looking for a way to prevent developers from modifying an existing changelog by adding/removing changesets. Liquibase defines a changeset as non-mutable; changing any parameter or dependency in a changeset will throw a violation error, but unfortunately, I do not see any way to prevent this from a changelog perspective.
Essentially, I'm trying to implement a convention that once a changelog is run, it can no longer be modified. New changesets must be added to a newer changelog instead.
Is there anyway I can accomplish this? How does everyone else manage non-mutability of changelogs?
liquibase
liquibase
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
asked Nov 16 '18 at 16:42
Eric B.Eric B.
10.3k29105216
10.3k29105216
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30
add a comment |
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53342083%2fhow-to-prevent-liquibase-from-executing-a-modified-version-of-the-changelog%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53342083%2fhow-to-prevent-liquibase-from-executing-a-modified-version-of-the-changelog%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you please elaborate on "once a changelog is run"? There are multiple environments where changelog/changesets will be executed. Some of them do not exist yet - think about a new colleague joining your team in one month and setting up his local environment. Should changelog be open for modifications until then?
– Illya Kysil
Nov 22 '18 at 20:07
@IllyaKysil Your comment made me think a bit, and I've come to realize that you're right. In my mind, the definition is once a changelog is executed on a particular system, that it cannot be re-executed a second time. But then what prevents someone from having modified it and running the modified version on a clean DB? Nothing. So with a little more thought, it makes sense that it is based on the changesets and not the changelog. Thanks.
– Eric B.
Nov 27 '18 at 23:30