Replies: 5 comments 13 replies
-
Btw, I love how Cloudflare did review apps super simple :-) |
Beta Was this translation helpful? Give feedback.
-
Hi @iBobik! Thanks for a very good questions. I'll in part answer however will raise a few questions to you as this is currently something we're looking more into.
Feel free to reach out in DMs if we can help to go around current Cloud limitations. Happy to work with you and make Cloud better for everyone! |
Beta Was this translation helpful? Give feedback.
-
Thank you for answer and info.Yes, you understand me correctly.Sharing tenant database is not critical issue for this workflow, because most projects will not need to test interaction with tenant API. It is just nice to have.Most critical is to streamline content database cloning. Ideally to solve all parts in one CLI command - create subproject, transfer database to it from live, add selected members to it (all, or e.g. with a role "testers" on a live project) and deploy frontend to a predictable subdomain (so it can be easily linked).This could be probably done with current API, it is just about usability. Unusable feature means it will not be used, or incorrectly, so people will test new featurest on live.
|
Beta Was this translation helpful? Give feedback.
-
Another use-case good to cover: I would like to protect live environment agains accidental db import, but allow import to review environments.
There should be some env variables on the cloud what can be used for things like this. Useable also for configuring webhooks baseurl etc. |
Beta Was this translation helpful? Give feedback.
-
Hi, I am experimenting with automated DB import on stage environment and end up with this error:
In Drupal and SQL database I usually added some schema changes and it's migrations scripts, commited it into the branch and let CI deploy it. It deployed code, imported DB dump from production (old schema) and then ran migration which migrated DB in the review environment. Then I was sure migration process will pass even on production when branch will be merged and the same migration script will be executed. So what steps the CI script should do with Contember to test new schema in the staging environment? This is my draft of the .gitlab-ci.yml which resulted in the error in
|
Beta Was this translation helpful? Give feedback.
-
Hi, for review environments I need to clone project wilt its database, including tenant database.
Current data import-export works only with content, but for proper testing I will need to test also with authentication, actions etc.
Is it possible? Or review apps workflow is possible only on a subproject level - content tables?
Btw, how deployment should look like to create subproject, copy database from live and apply migrations to this new project?
Can I have single deployment token for all projects?
Beta Was this translation helpful? Give feedback.
All reactions