drupalSite-operator merge requestshttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests2023-10-17T18:49:23+02:00https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/210Revert "Merge branch 'revert-b20d7ac8' into 'master'"2023-10-17T18:49:23+02:00Carina AntunesRevert "Merge branch 'revert-b20d7ac8' into 'master'"This reopens revert merge request !209
php-fpm logs:
```
+ LIVENESS_PROBE_FAILURE_FILE=/var/run/liveness_probe_failure
+ '[' -f /var/run/liveness_probe_failure ]
+ exec php-fpm
+ drush state-get system.cron_key '--format=string'
[17-Oc...This reopens revert merge request !209
php-fpm logs:
```
+ LIVENESS_PROBE_FAILURE_FILE=/var/run/liveness_probe_failure
+ '[' -f /var/run/liveness_probe_failure ]
+ exec php-fpm
+ drush state-get system.cron_key '--format=string'
[17-Oct-2023 16:45:08] ERROR: [/usr/local/etc/php-fpm.d/zz-docker.conf:12] unknown entry 'error_log_format'
[17-Oct-2023 16:45:08] ERROR: Unable to include /usr/local/etc/php-fpm.d/zz-docker.conf from /usr/local/etc/php-fpm.conf at line 12
[17-Oct-2023 16:45:08] ERROR: failed to load configuration file '/usr/local/etc/php-fpm.conf'
[17-Oct-2023 16:45:08] ERROR: FPM initialization failed
```Francisco Borges Aurindo BarrosFrancisco Borges Aurindo Barroshttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/204WIP: Have automatic backups before processing deletion2024-03-26T12:02:42+01:00Francisco Borges Aurindo BarrosWIP: Have automatic backups before processing deletionThis MR will create and wait for a final backup of an instance before processing the deletion.
Part of issue: https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/90This MR will create and wait for a final backup of an instance before processing the deletion.
Part of issue: https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/90https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/188[#91] Update Route handling to comply with custom domains2023-09-20T15:24:10+02:00Francisco Borges Aurindo Barros[#91] Update Route handling to comply with custom domainsCurrently routes are created and have enforced values, as per [operator's code](https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/blob/master/controllers/drupalsite_resources.go#L1231).
Since the operator should support and maint...Currently routes are created and have enforced values, as per [operator's code](https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/blob/master/controllers/drupalsite_resources.go#L1231).
Since the operator should support and maintain custom domains when required, example on the following Ticket [RQF2102204](https://cern.service-now.com/service-portal?id=ticket&n=RQF2102204), this MR goal is to update the Operator to act accordingly when that's the case.
To summarize:
- Route configuration remains the same when it's a *.cern or *.web.cern.ch domain
- Any other domain and `TLS` field is not enforced, leaving it to another component to do it. As of 07/09/2022 that would be the [openshift-acme](https://gitlab.cern.ch/paas-tools/okd4-deployment/openshift-acme), that will change once this [issue](https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/1030) is handled but since the new component does not present enough maturity, there is no ETA for the new component.https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/180Buildconfig update on reconciliation2022-05-09T11:34:51+02:00Vineet Reddy RajulaBuildconfig update on reconciliationFixes https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/884Fixes https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/884https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/138Draft: Fix install job creation2021-11-30T12:49:25+01:00Konstantinos Samaras-TsakirisDraft: Fix install job creationAfter changing the install job name in https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/137 , I noticed that the new install job was being created for already-installed sites. This is dangerous!
- Added a check o...After changing the install job name in https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/merge_requests/137 , I noticed that the new install job was being created for already-installed sites. This is dangerous!
- Added a check on the `Initialized` condition before ensuring the install job.
- Fixed the Initialized condition. It used to be set to `false` even if the operator simply failed to exec into the pod, which is unintended. Instead, it should be `Unknown`.Vineet Reddy RajulaVineet Reddy Rajula