All these messages (and the error «The file “/composer.json” doesn’t exist» message) are generated by an unknown black-box closed source script/program:
Building application ‘mymagento’ (runtime type: php:7.0, tree ID: 4be8741)
Generating runtime configuration.
Moving the application to the output directory
W: Overriding path robots.txt that already exists in destination.
Prewarming composer cache.
Pre-downloaded 2 packages referenced in composer.lock
These strings are absent in your beta and production websites source code.
So the only way to investigate the case and this unknown black-box closed source program requirements is to contact the program author - Magento Enterprise team.
Ask them:
Where is exactly the «The file “/composer.json” doesn’t exist» message generated?
Why is the message generated? What are the hidden requirements about such «composer.json» files?
All these messages (and the error «The file “/composer.json” doesn’t exist» message) are generated by an unknown black-box closed source script/program
If you want to prove opposite, then provide THE EXACT source code where these messages are generated.
So what am I supposed to do with this? Only solution offered so far by magento is remove module … is that where we leave this ? When I do remove stripe the Magento cloud deploy Process does in fact work as they say …
It’s not hard to understand, its just not a real answer. Magento says this:
Vidal Yesterday at 00:34
Hello Sam,
Unfortunately, the creator of the extension must determine the cause of the issue between Magento and the extension. The integration of any 3rd party application is the responsibility of the SI and/or the creator of the extension.
Best,
Vidal
Meanwhile we can’t even deploy Magento to the Cloud without removing Stripe our pay processor. And neither you or Magento seem to care.
All my extensions are 100% Open Source and published on GitHub: https://github.com/mage2pro
So they can be easily explored and debugged by other developers and customers.
Magento Enterprise Cloud is a closed source and undocumented (!) service with (as you said) 2 weeks delay in customer support.
I do not know what is the cause of your issue, and I do not have any ability to debug it because of lack of the Cloud’s source code and specification.
I recommend you just leave Magento Cloud and use your own server, which you can control and debug.
Hey!
Look at the error I was just able to reproduce in a docker container. It happened when I disabled all modules from command line and then re-able them. Magento-Cloud does exactly this when it deploys. Does this help figure out why that error shows up? It does not look specific to Magento-cloud anymore…