How to move to previous version of stack using cloudformation?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















Usecase



I have cloudformation template with resources and lambda functions . Usually the cloudformation will rollback the stack when there is failure in creating it.



But what if i had pushed some resources or lambda functions with wrong logic or with less configurations . In such case i want to rollback the stack to previous working stack.



I Know i have rollback triggers to monitor my stack and trigger alarms. But i want to do it manually because, what if i had missing that test scenario and because of that the alarms not triggered.



Is it possible with cloudformation ?



Thanks
Any help is appreciated










share|improve this question























  • Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

    – petrch
    Nov 24 '18 at 12:50


















0















Usecase



I have cloudformation template with resources and lambda functions . Usually the cloudformation will rollback the stack when there is failure in creating it.



But what if i had pushed some resources or lambda functions with wrong logic or with less configurations . In such case i want to rollback the stack to previous working stack.



I Know i have rollback triggers to monitor my stack and trigger alarms. But i want to do it manually because, what if i had missing that test scenario and because of that the alarms not triggered.



Is it possible with cloudformation ?



Thanks
Any help is appreciated










share|improve this question























  • Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

    – petrch
    Nov 24 '18 at 12:50














0












0








0








Usecase



I have cloudformation template with resources and lambda functions . Usually the cloudformation will rollback the stack when there is failure in creating it.



But what if i had pushed some resources or lambda functions with wrong logic or with less configurations . In such case i want to rollback the stack to previous working stack.



I Know i have rollback triggers to monitor my stack and trigger alarms. But i want to do it manually because, what if i had missing that test scenario and because of that the alarms not triggered.



Is it possible with cloudformation ?



Thanks
Any help is appreciated










share|improve this question














Usecase



I have cloudformation template with resources and lambda functions . Usually the cloudformation will rollback the stack when there is failure in creating it.



But what if i had pushed some resources or lambda functions with wrong logic or with less configurations . In such case i want to rollback the stack to previous working stack.



I Know i have rollback triggers to monitor my stack and trigger alarms. But i want to do it manually because, what if i had missing that test scenario and because of that the alarms not triggered.



Is it possible with cloudformation ?



Thanks
Any help is appreciated







amazon-web-services amazon-cloudformation






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 23 '18 at 18:14









PrivatePrivate

514617




514617













  • Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

    – petrch
    Nov 24 '18 at 12:50



















  • Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

    – petrch
    Nov 24 '18 at 12:50

















Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

– petrch
Nov 24 '18 at 12:50





Just update with the previous version of your deployment. If you use git or other version control it should be easy to just checkout the previous version and update with that one.

– petrch
Nov 24 '18 at 12:50












1 Answer
1






active

oldest

votes


















0














No you can't do that with Cloudformation.



Your CD pipeline should keep track of any code builds and template configuration and you should rollback with old/archived code by pushing out a new stack with that old code.






share|improve this answer
























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451334%2fhow-to-move-to-previous-version-of-stack-using-cloudformation%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    No you can't do that with Cloudformation.



    Your CD pipeline should keep track of any code builds and template configuration and you should rollback with old/archived code by pushing out a new stack with that old code.






    share|improve this answer




























      0














      No you can't do that with Cloudformation.



      Your CD pipeline should keep track of any code builds and template configuration and you should rollback with old/archived code by pushing out a new stack with that old code.






      share|improve this answer


























        0












        0








        0







        No you can't do that with Cloudformation.



        Your CD pipeline should keep track of any code builds and template configuration and you should rollback with old/archived code by pushing out a new stack with that old code.






        share|improve this answer













        No you can't do that with Cloudformation.



        Your CD pipeline should keep track of any code builds and template configuration and you should rollback with old/archived code by pushing out a new stack with that old code.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 20 at 11:26









        MariuszMariusz

        211




        211
































            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451334%2fhow-to-move-to-previous-version-of-stack-using-cloudformation%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?