Lambda versions are incremented even i delete the lambda stack(ie.CFN)?












0














I am publishing the NEW lambda version for each of my each lambda function in my cloudformation template using custom resource . This invokes when ever there is an update to the lambda function.



I have two lambda functions in my stack(i.e.STACK1) which are created using CFN template. There Arn's are like this .



arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:1
arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:1


After few updates to my stack(i.e.'STACK1`) it became like this



arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:5
arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:2


Next Step, i had deleted the above stack(i.e.'STACK1) and created a new stack with different name(i.e.'STACK2). When i see the created ARN's of the lambda functions they are like this



arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:6
arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:3


Even i deleted the stack and created a new one with new name i dont know why these lambda ARN's versions are incremented.



When i digged this issue deep , i had found that it is published based on the fuctionname so when i changed the function name then it started with version 1.
Even deleting the stack, is not deleting the versions on the function because of that when i used the same function name it is taking the functions version.



I also checked the lambdas are present or not in lambda console just to double check whether cloudformation is deleting it or not . Yes, Cloudformation is deleting it.



How can i able to avoid this scenario ??




BTW: This situation is not occuring when i allow AWS to define my
lambda function name.




Thanks.
Any help is appreciated










share|improve this question



























    0














    I am publishing the NEW lambda version for each of my each lambda function in my cloudformation template using custom resource . This invokes when ever there is an update to the lambda function.



    I have two lambda functions in my stack(i.e.STACK1) which are created using CFN template. There Arn's are like this .



    arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:1
    arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:1


    After few updates to my stack(i.e.'STACK1`) it became like this



    arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:5
    arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:2


    Next Step, i had deleted the above stack(i.e.'STACK1) and created a new stack with different name(i.e.'STACK2). When i see the created ARN's of the lambda functions they are like this



    arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:6
    arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:3


    Even i deleted the stack and created a new one with new name i dont know why these lambda ARN's versions are incremented.



    When i digged this issue deep , i had found that it is published based on the fuctionname so when i changed the function name then it started with version 1.
    Even deleting the stack, is not deleting the versions on the function because of that when i used the same function name it is taking the functions version.



    I also checked the lambdas are present or not in lambda console just to double check whether cloudformation is deleting it or not . Yes, Cloudformation is deleting it.



    How can i able to avoid this scenario ??




    BTW: This situation is not occuring when i allow AWS to define my
    lambda function name.




    Thanks.
    Any help is appreciated










    share|improve this question

























      0












      0








      0







      I am publishing the NEW lambda version for each of my each lambda function in my cloudformation template using custom resource . This invokes when ever there is an update to the lambda function.



      I have two lambda functions in my stack(i.e.STACK1) which are created using CFN template. There Arn's are like this .



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:1
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:1


      After few updates to my stack(i.e.'STACK1`) it became like this



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:5
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:2


      Next Step, i had deleted the above stack(i.e.'STACK1) and created a new stack with different name(i.e.'STACK2). When i see the created ARN's of the lambda functions they are like this



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:6
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:3


      Even i deleted the stack and created a new one with new name i dont know why these lambda ARN's versions are incremented.



      When i digged this issue deep , i had found that it is published based on the fuctionname so when i changed the function name then it started with version 1.
      Even deleting the stack, is not deleting the versions on the function because of that when i used the same function name it is taking the functions version.



      I also checked the lambdas are present or not in lambda console just to double check whether cloudformation is deleting it or not . Yes, Cloudformation is deleting it.



      How can i able to avoid this scenario ??




      BTW: This situation is not occuring when i allow AWS to define my
      lambda function name.




      Thanks.
      Any help is appreciated










      share|improve this question













      I am publishing the NEW lambda version for each of my each lambda function in my cloudformation template using custom resource . This invokes when ever there is an update to the lambda function.



      I have two lambda functions in my stack(i.e.STACK1) which are created using CFN template. There Arn's are like this .



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:1
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:1


      After few updates to my stack(i.e.'STACK1`) it became like this



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:5
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:2


      Next Step, i had deleted the above stack(i.e.'STACK1) and created a new stack with different name(i.e.'STACK2). When i see the created ARN's of the lambda functions they are like this



      arn:aws:lambda:us-east-1:xxxx:function:Pikachuu:6
      arn:aws:lambda:us-east-1:xxxx:function:Pythachuu:3


      Even i deleted the stack and created a new one with new name i dont know why these lambda ARN's versions are incremented.



      When i digged this issue deep , i had found that it is published based on the fuctionname so when i changed the function name then it started with version 1.
      Even deleting the stack, is not deleting the versions on the function because of that when i used the same function name it is taking the functions version.



      I also checked the lambdas are present or not in lambda console just to double check whether cloudformation is deleting it or not . Yes, Cloudformation is deleting it.



      How can i able to avoid this scenario ??




      BTW: This situation is not occuring when i allow AWS to define my
      lambda function name.




      Thanks.
      Any help is appreciated







      amazon-web-services aws-lambda






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 11:14









      Private

      451516




      451516
























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


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53410914%2flambda-versions-are-incremented-even-i-delete-the-lambda-stackie-cfn%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
















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f53410914%2flambda-versions-are-incremented-even-i-delete-the-lambda-stackie-cfn%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

          Wiesbaden

          Marschland

          Dieringhausen