How do I restore Magento Cloud environments deleted by GitHub integration?












0















I followed the instructions to setup a GitHub integration with my Magento Cloud Pro project. This project has not been made live yet, but has been in development for several months and therefore has 1k+ commits. I took a snapshot of my Integration environment and ran the command as documented:



magento-cloud integration:add --type=github --project ...


There were additional prompts that appeared after running, with what seemed to be reasonable defaults, which I accepted.



Build pull requests (--build-pull-requests)
Build every pull request as an environment? [Y|n]

Build pull requests post-merge (--build-pull-requests-post-merge)
Build pull requests based on their post-merge state? [y|N]

Clone data for pull requests (--pull-requests-clone-parent-data)
Clone the parent environment's data for pull requests? [Y|n]

Fetch branches (--fetch-branches)
Fetch all branches from the remote (as inactive environments)? [Y|n]

Prune branches (--prune-branches)
Delete branches that do not exist on the remote? [Y|n]


After the last question it created a webhook and created the integration.



Oh, then it deleted all my environments apart from Master, Production, and Staging.



Bye bye bye



I'm guessing it's the last prompt that screwed me up --prune-branches. Shame on me for not pausing to consider what that might do (note: this option isn't documented in the instructions).



What can I do to restore these environments?



Unlike deleting an environment through the Magento Cloud GUI, these appear to be gone. They aren't there and deactivated.









share



























    0















    I followed the instructions to setup a GitHub integration with my Magento Cloud Pro project. This project has not been made live yet, but has been in development for several months and therefore has 1k+ commits. I took a snapshot of my Integration environment and ran the command as documented:



    magento-cloud integration:add --type=github --project ...


    There were additional prompts that appeared after running, with what seemed to be reasonable defaults, which I accepted.



    Build pull requests (--build-pull-requests)
    Build every pull request as an environment? [Y|n]

    Build pull requests post-merge (--build-pull-requests-post-merge)
    Build pull requests based on their post-merge state? [y|N]

    Clone data for pull requests (--pull-requests-clone-parent-data)
    Clone the parent environment's data for pull requests? [Y|n]

    Fetch branches (--fetch-branches)
    Fetch all branches from the remote (as inactive environments)? [Y|n]

    Prune branches (--prune-branches)
    Delete branches that do not exist on the remote? [Y|n]


    After the last question it created a webhook and created the integration.



    Oh, then it deleted all my environments apart from Master, Production, and Staging.



    Bye bye bye



    I'm guessing it's the last prompt that screwed me up --prune-branches. Shame on me for not pausing to consider what that might do (note: this option isn't documented in the instructions).



    What can I do to restore these environments?



    Unlike deleting an environment through the Magento Cloud GUI, these appear to be gone. They aren't there and deactivated.









    share

























      0












      0








      0








      I followed the instructions to setup a GitHub integration with my Magento Cloud Pro project. This project has not been made live yet, but has been in development for several months and therefore has 1k+ commits. I took a snapshot of my Integration environment and ran the command as documented:



      magento-cloud integration:add --type=github --project ...


      There were additional prompts that appeared after running, with what seemed to be reasonable defaults, which I accepted.



      Build pull requests (--build-pull-requests)
      Build every pull request as an environment? [Y|n]

      Build pull requests post-merge (--build-pull-requests-post-merge)
      Build pull requests based on their post-merge state? [y|N]

      Clone data for pull requests (--pull-requests-clone-parent-data)
      Clone the parent environment's data for pull requests? [Y|n]

      Fetch branches (--fetch-branches)
      Fetch all branches from the remote (as inactive environments)? [Y|n]

      Prune branches (--prune-branches)
      Delete branches that do not exist on the remote? [Y|n]


      After the last question it created a webhook and created the integration.



      Oh, then it deleted all my environments apart from Master, Production, and Staging.



      Bye bye bye



      I'm guessing it's the last prompt that screwed me up --prune-branches. Shame on me for not pausing to consider what that might do (note: this option isn't documented in the instructions).



      What can I do to restore these environments?



      Unlike deleting an environment through the Magento Cloud GUI, these appear to be gone. They aren't there and deactivated.









      share














      I followed the instructions to setup a GitHub integration with my Magento Cloud Pro project. This project has not been made live yet, but has been in development for several months and therefore has 1k+ commits. I took a snapshot of my Integration environment and ran the command as documented:



      magento-cloud integration:add --type=github --project ...


      There were additional prompts that appeared after running, with what seemed to be reasonable defaults, which I accepted.



      Build pull requests (--build-pull-requests)
      Build every pull request as an environment? [Y|n]

      Build pull requests post-merge (--build-pull-requests-post-merge)
      Build pull requests based on their post-merge state? [y|N]

      Clone data for pull requests (--pull-requests-clone-parent-data)
      Clone the parent environment's data for pull requests? [Y|n]

      Fetch branches (--fetch-branches)
      Fetch all branches from the remote (as inactive environments)? [Y|n]

      Prune branches (--prune-branches)
      Delete branches that do not exist on the remote? [Y|n]


      After the last question it created a webhook and created the integration.



      Oh, then it deleted all my environments apart from Master, Production, and Staging.



      Bye bye bye



      I'm guessing it's the last prompt that screwed me up --prune-branches. Shame on me for not pausing to consider what that might do (note: this option isn't documented in the instructions).



      What can I do to restore these environments?



      Unlike deleting an environment through the Magento Cloud GUI, these appear to be gone. They aren't there and deactivated.







      magento2 cli cloud github





      share












      share










      share



      share










      asked 1 min ago









      nachitonachito

      558414




      558414






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "479"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2fmagento.stackexchange.com%2fquestions%2f258269%2fhow-do-i-restore-magento-cloud-environments-deleted-by-github-integration%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 Magento Stack Exchange!


          • 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%2fmagento.stackexchange.com%2fquestions%2f258269%2fhow-do-i-restore-magento-cloud-environments-deleted-by-github-integration%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

          Polycentropodidae

          Magento 2 Error message: Invalid state change requested

          Paulmy