drupal issueshttps://gitlab.cern.ch/groups/drupal/-/issues2024-03-27T15:54:00+01:00https://gitlab.cern.ch/drupal/paas/drupal-operations/-/issues/11Block module/theme installation on new Drupal instances2024-03-27T15:54:00+01:00Francisco Borges Aurindo BarrosBlock module/theme installation on new Drupal instancesThe goal is to disallow any level of customization to the Drupal administrators.
To achieve this, we must block module installation.
Current possible options:
## 1. Change deployment setup
##### Description:
The deployment would have...The goal is to disallow any level of customization to the Drupal administrators.
To achieve this, we must block module installation.
Current possible options:
## 1. Change deployment setup
##### Description:
The deployment would have PVs mounted as read-only for `/drupal-data/modules` and `/drupal-data/themes` paths on `webdav` container.
##### Pros:
It is uniform to all users. New instances will have no customization, existing instances will not be able to add any new customizations, but keep current ones.
##### Cons:
Once applied, modules cannot be updated neither removed by users. It will require admin action or access to the `php-fpm` container in order to do full `CRUD` operations.
Users that have requested advanced access to containers will continue to be able to add modules. Revoking access to previously given users would be advisable.
Extra: We can have a label to make it `ready-write` mount on `webdav` for necessary exceptions for a temporary time. I would not recommend this, but can be included if we are to go with this path but multiple expecting exceptions.
## 2. Separate new image
##### Description:
We can have a default image, and the only available for new instances, that does not do any linkage of `/drupal-data/modules` to be actually used as modules. This linkage is embedded in the image, and if removed, would make the customization impossible to users.
##### Pros:
Clear distinction between websites with and without customization available. Fully working for the first, zero for the latter.
##### Cons:
Maintain two `RELEASE` images for the time being, and have to update both.https://gitlab.cern.ch/drupal/paas/drupal-operations/-/issues/10Draft: Forbid adding custom modules to new Drupal websites2024-03-19T09:29:23+01:00Francisco Borges Aurindo BarrosDraft: Forbid adding custom modules to new Drupal websitesAfter the ED meeting, we can now start by blocking Drupal websites from installing modules that are not in the cern-drupal-distribution.
There are many considerations to take into account:
- Can only affect new instances
- Drupal does ...After the ED meeting, we can now start by blocking Drupal websites from installing modules that are not in the cern-drupal-distribution.
There are many considerations to take into account:
- Can only affect new instances
- Drupal does not seem to have any easy locking/disabling of the installation button (maybe a custom development might be required and added to the installation page)
- Filesystem lock on the image might affect existing websiteshttps://gitlab.cern.ch/drupal/paas/drupal-operations/-/issues/9Migrating from DrupalLB to LBaaS2024-03-27T12:06:43+01:00Francisco Borges Aurindo BarrosMigrating from DrupalLB to LBaaSDue to several reasons, we are now planning a smooth transition from the drupal loadbalancers to LBaaS.
The current setup has the follow:
- One static IPv4 and IPv6 (188.184.37.219 and 2001:1458:201:b0::100:1b)
- One machine handling t...Due to several reasons, we are now planning a smooth transition from the drupal loadbalancers to LBaaS.
The current setup has the follow:
- One static IPv4 and IPv6 (188.184.37.219 and 2001:1458:201:b0::100:1b)
- One machine handling the loadbalancing (Currently `drupal8p11`, but due to floating IP, a new machine can assume the work once this one fails the liveness probing)
Thus, the requirement for IPv6 and static IPs were a must when looking into LBaaS.
Since the requirements are met, the following is a proposed set of actions to do a transparent migration to the new LBs.
## Preparation and Requirements
- [x] Meet with the LBaaS team and assess the state of the service and load handling
- [ ] Prepare inventory of all domains and redirections served in DrupalLB
- [ ] Prepare inventory of domains already served in paas and drupal
- [ ] Investigate if all redirections are supported on new infra. Plan implementation of redirections if needed
- [ ] Prepare plan for move of domains: configuration of domains and redirections manual or automated? Coordination of DNS with Veronique needed? Batches? Dates. Devise procedure to validate, monitoring. Devise steps to rollback in case of need, shorter TTLs needed during migration in case of rollback needed?
- [ ] Standardise TTL of .cern domains with Veronique (30 minutes?)
- [ ] Configure new LBaaS for Drupal
- [ ] Create a new Octavia LoadBalancers (v2) in the critical area, to be used by all '.cern' projects and with custom domains
Steps described here: https://okd-internal.docs.cern.ch/components/cloud-controller/
- [ ] Add it to the configuration
Similar configuration required after: https://gitlab.cern.ch/paas-tools/okd4-install/-/blob/master/chart/values-paas.yaml?ref_type=heads#L338-L359
- [ ] Create a new project using the new LBaaS instance
- [ ] Stress test the new project, confirm load capacity
- [ ] Have a failover request while already handling some .cern traffic (before home.cern) and coordinate with the LBaaS team
- [ ] Test, document and validate the LBaaS failover mechanism
- [ ] Create OTG for dates decided
- [ ] Have home.cern and others with the annotation for `all` instances while the change is being done`*`
- [ ] Update namespaces with `apps-lb-crit` value once the change has been done fully
`*`
_Reason why we will have temporarily `all` annotation of loadbalancing:_
```mermaid
flowchart TD;
A[User] --> B[Old LB];
B --> C[Apps-Shard-1];
A --> D[Apps-lb-crit];
```
We currently have the flow on the left (through old LB infra), and we want the final state to be the one on the right (directly to apps-lb-crit). But due to DNS update time, for a while both flows will have to work, which means the namespace has to accept requests coming from both `apps-shard-` and `apps-lb-crit`. This is the point in time we use `all`, so that during the transition period both flows will work for the users.
## Procedure
Once the setup is ready, request change of DNS records for the multiple `.cern` domains, preferably leaving `home.cern` for last in case a rollback is required.
We should talk directly with Veronique to coordinate.
**We use the move as an opportunity to standardize DNS TTL records and request lower times (currently it can be up to 12h to update DNS records globally)**
During this period, all that is required is monitoring and validating that traffic is not affected.
## Cleanup
Delete the following projects and their redirections:
- cixp-redirect (paas), currently serving www.cixp.net, and migrate the DNS record to the new LBaaS
- oqi-cern (drupal), currently handles oqi.cern redirection
[More instances to be added]
Notes from discussion about design:
https://docs.google.com/document/d/1lKyuafnnFKP5Yd_GQE8cx9QFamMa4g3IV27byKGhsCE/edit?usp=sharing
---
# Timeline
|Time|Step|
|---|---|
| February | Start LBaaS migration plan |
| First half of March | Discuss with LBaaS team and communicate plan |
| Second half of March | Provision new LB instance and start point some cern domains onto it |
| April | Full migration of dot cern domains |
| May | Decomission of old infrastructure |https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/95Clone behind SSO2024-02-14T15:25:02+01:00Carina AntunesClone behind SSOhttps://gitlab.cern.ch/drupal/paas/drupal-operations/-/issues/8Update Matomo configurations2024-03-27T00:05:01+01:00Francisco Borges Aurindo BarrosUpdate Matomo configurationsPete has reported that multiple Drupal websites have their IDs updated, but still pointing to the Piwik (old).
The task is to update the endpoint with the new URL, `https://webanalytics.web.cern.ch/`.
The list to be processed is the fol...Pete has reported that multiple Drupal websites have their IDs updated, but still pointing to the Piwik (old).
The task is to update the endpoint with the new URL, `https://webanalytics.web.cern.ch/`.
The list to be processed is the following one:
```
https://ep-news.web.cern.ch/ 248
https://atlas.cern/ 227
https://root.cern/ 115
https://epc-ccs.web.cern.ch (http://sy-dep-epc.web.cern.ch) 246
http://clear.cern/ 300
https://atlas-secretariat.web.cern.ch/ 301
https://careers.cern/ 385
https://ippog.org/ 224
https://cnpdfs.web.cern.ch/ 372
```https://gitlab.cern.ch/drupal/paas/drupal-operations/-/issues/7Cleanup clones 20242024-03-28T09:29:36+01:00Carina AntunesCleanup clones 2024Vasvi SharmaVasvi Sharmahttps://gitlab.cern.ch/drupal/paas/cern-drupal-distribution/-/issues/25Blacklist modules2024-03-27T00:05:01+01:00Carina AntunesBlacklist modulesGiving the most recent critical security vulnerability detected, https://www.drupal.org/sa-core-2023-006,
a question arose regarding the possibility to backlist a module, until a patch is applied.
After investigation, it appears out of...Giving the most recent critical security vulnerability detected, https://www.drupal.org/sa-core-2023-006,
a question arose regarding the possibility to backlist a module, until a patch is applied.
After investigation, it appears out of the box, this feature is not possible, however there's a module which provides said functionality.
I propose we add to our distribution https://www.drupal.org/project/module_blacklist.
The module allows site administrators to block certain module from being installed, based on a blacklist set on settings.php file.
In this case simply adding the mentioned module, results in blocking fresh installations of said module.
```
$settings['module_blacklist'] = [
'jsonapi',
];
```
![Screenshot_2023-09-21_at_11.42.45](/uploads/2d9144536f5d59403d638c100642ca66/Screenshot_2023-09-21_at_11.42.45.png)
It does not block already installed modules, which can be discussed further.
Related to this topic, the following module, can be particularly interesting for websites still in PHP 7, and to Drupal 10 beyond EOL:
- https://www.drupal.org/project/readonlymodehttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/91Update Route handling to comply with custom domains2024-03-27T00:05:01+01:00Carina AntunesUpdate 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.Francisco Borges Aurindo BarrosFrancisco Borges Aurindo Barroshttps://gitlab.cern.ch/drupal/paas/renovate-bot/-/issues/2Dependency Dashboard2023-10-16T08:04:43+02:00Cern Drupal Distribution UserDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detect...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
</details>
</blockquote>
</details>https://gitlab.cern.ch/drupal/paas/cern-drupal-distribution/-/issues/21Repo Dependency Dashboard for Renovate Bot2024-03-16T08:05:32+01:00Cern Drupal Distribution UserRepo Dependency Dashboard for Renovate BotThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Repository problems
These problems occurred while renovating this...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
## Repository problems
These problems occurred while renovating this repository.
- WARN: GitHub token is required for some dependencies
- WARN: No github.com token has been configured. Skipping release notes retrieval
## Edited/Blocked
These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.
- [ ] <!-- rebase-branch=renovate-all-dependencies -->[Update all dependencies](!207) (`@playwright/test`, `@types/node`, `bower-asset/bootstrap`, `drupal/features`, `drupal/ui_patterns_ds`, `drupal/ui_patterns_field_group`, `drupal/ui_patterns_layouts`, `drupal/ui_patterns_library`, `drush/drush`, `mcr.microsoft.com/playwright`, `npm-asset/jquery`, `wikimedia/composer-merge-plugin`)
---
### ⚠ Dependency Lookup Warnings ⚠
- Renovate failed to look up the following dependencies: `Failed to look up packagist package drupal/cern-adminimal-subtheme`, `Failed to look up packagist package drupal/cern-base-theme`, `Failed to look up packagist package drupal/cern-cds-media`, `Failed to look up packagist package drupal/cern-components`, `Failed to look up packagist package drupal/cern-dev-status`, `Failed to look up packagist package drupal/cern-display-formats`, `Failed to look up packagist package drupal/cern-full-html-format`, `Failed to look up packagist package drupal/cern-indico-feeds`, `Failed to look up packagist package drupal/cern-install-profiles`, `Failed to look up packagist package drupal/cern-integration`, `Failed to look up packagist package drupal/cern-landing-page`, `Failed to look up packagist package drupal/cern-ldap-api`, `Failed to look up packagist package drupal/cern-loading`, `Failed to look up packagist package drupal/cern-paragraph-types`, `Failed to look up packagist package drupal/cern-profile-displayname`, `Failed to look up packagist package drupal/cern-theme`, `Failed to look up packagist package drupal/cern-toolbar`, `Failed to look up packagist package drupal/cern-webcast-feeds`, `Failed to look up packagist package drupal/cern-webform-invitation`.
Files affected: `composer.json`
---
## Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- [ ] <!-- rebase-branch=renovate-drupal-core -->[Update drupal core to v10.2.4](!239) (`drupal/core-composer-scaffold`, `drupal/core-project-message`, `drupal/core-recommended`)
## Detected dependencies
<details><summary>composer</summary>
<blockquote>
<details><summary>composer.json</summary>
- `bower-asset/bootstrap ~5.1.0`
- `bower-asset/jquery-cycle ~3.0.0`
- `bower-asset/jquery-hoverintent ~1.10.0`
- `composer/installers ^2.2`
- `cweagans/composer-patches ^1.7`
- `dompdf/dompdf ^2.0`
- `drupal/adminimal_theme ^1.7`
- `drupal/admin_toolbar ^3.2`
- `drupal/aggregator ^2.1`
- `drupal/allowed_formats ^3.0`
- `drupal/bartik ^1.0`
- `drupal/bootstrap ^3.25`
- `drupal/captcha ^2.0`
- `drupal/cern-adminimal-subtheme ~3.0.1`
- `drupal/cern-base-theme ~3.0.2`
- `drupal/cern-cds-media ~3.0.3`
- `drupal/cern-components ~3.0.19`
- `drupal/cern-dev-status ~3.1.1`
- `drupal/cern-display-formats ~3.0.1`
- `drupal/cern-full-html-format ~3.0.2`
- `drupal/cern-indico-feeds ~3.0.1`
- `drupal/cern-install-profiles 9.0.2`
- `drupal/cern-integration ~2.0.0`
- `drupal/cern-landing-page ~3.0.4`
- `drupal/cern-ldap-api ~3.0.0`
- `drupal/cern-loading ~3.0.0`
- `drupal/cern-paragraph-types ~3.0.2`
- `drupal/cern-profile-displayname ~3.0.0`
- `drupal/cern-theme ~3.0.0`
- `drupal/cern-toolbar ~3.1.1`
- `drupal/cern-webcast-feeds ~3.0.3`
- `drupal/cern-webform-invitation ~3.0.1`
- `drupal/ckeditor_font ^2.0@beta`
- `drupal/codesnippet ^1.8`
- `drupal/color ^1.0`
- `drupal/color_field ^3.0`
- `drupal/colorbox ^2.0`
- `drupal/colorbutton ^1.4`
- `drupal/components ^3.0@beta`
- `drupal/config_update 2.0.0-alpha3`
- `drupal/content_access ^2.0@RC`
- `drupal/core-composer-scaffold 10.1.8`
- `drupal/core-project-message 10.1.8`
- `drupal/core-recommended 10.1.8`
- `drupal/ctools ^4.0`
- `drupal/date_popup ^2.0`
- `drupal/devel ^5.0`
- `drupal/ds ^3.15`
- `drupal/easy_breadcrumb ^2.0`
- `drupal/entity_browser ^2.8`
- `drupal/entity_print ^2.7`
- `drupal/entity_reference_revisions ^1.10`
- `drupal/externalauth ^2.0`
- `drupal/extlink ^1.7`
- `drupal/facets ^2.0`
- `drupal/features 3.13.0`
- `drupal/feeds ^3.0@beta`
- `drupal/feeds_ex ^1.0@beta`
- `drupal/fences ^3.0`
- `drupal/field_formatter_class ^1.6`
- `drupal/field_group ^3.3`
- `drupal/field_permissions ^1.2`
- `drupal/filefield_paths ~1.0@beta`
- `drupal/filelog 2.1.1`
- `drupal/honeypot ^2.1`
- `drupal/hook_event_dispatcher ^4.0@beta`
- `drupal/imagemagick ^3.4`
- `drupal/imce ^3.0`
- `drupal/jquery_ui 1.6.0`
- `drupal/jquery_ui_accordion 2.0.0`
- `drupal/jquery_ui_datepicker 2.0.0`
- `drupal/jquery_ui_draggable 2.0.0`
- `drupal/jquery_ui_droppable 2.0.0`
- `drupal/mailsystem ^4.4`
- `drupal/matomo ^1.19`
- `drupal/memcache ^2.5`
- `drupal/menu_block ^1.8`
- `drupal/menu_breadcrumb ^1.16`
- `drupal/metatag ^2.0`
- `drupal/migrate_tools ^6.0`
- `drupal/migrate_upgrade ^4.0`
- `drupal/module_filter ^4.0`
- `drupal/node_view_permissions ^1.5`
- `drupal/openid_connect ^3.0@alpha`
- `drupal/panelbutton ^1.5`
- `drupal/paragraphs ^1.16.0`
- `drupal/pathauto ^1.11`
- `drupal/permissions_by_term ^3.1`
- `drupal/quickedit ^1.0`
- `drupal/r4032login ^2.2`
- `drupal/rdf ^2.1`
- `drupal/recaptcha 3.2.0`
- `drupal/redirect ^1.9`
- `drupal/require_login ^3.0`
- `drupal/rules ^3.0@alpha`
- `drupal/scheduler ^2.0`
- `drupal/search_api ^1.27`
- `drupal/seven ^1.0`
- `drupal/smart_trim ^2.0`
- `drupal/token ^1.11`
- `drupal/twig_tweak ^3.2`
- `drupal/panels ^4.7`
- `drupal/ui_patterns ^1.7`
- `drupal/ui_patterns_ds ~1.7.0`
- `drupal/ui_patterns_field_group ~1.7.0`
- `drupal/ui_patterns_layouts ~1.7.0`
- `drupal/ui_patterns_library ~1.7.0`
- `drupal/upgrade_status ^4.0`
- `drupal/userprotect ~1.2.0`
- `drupal/views_bulk_operations ^4.2`
- `drupal/views_slideshow ~5.0.0`
- `drupal/views_taxonomy_term_name_depth ^7.1`
- `drupal/viewsreference ^1.8`
- `drupal/webform ^6.2`
- `drush/drush 12.1.2`
- `npm-asset/jquery ~3.6.0`
- `vlucas/phpdotenv ^5.5`
- `webflo/drupal-finder ~1.2.0`
- `webmozart/path-util ^2.3`
- `wikimedia/composer-merge-plugin ~2.0.1`
- `zaporylie/composer-drupal-optimizations ^1.2`
</details>
</blockquote>
</details>
<details><summary>dockerfile</summary>
<blockquote>
<details><summary>images/Dockerfile-composerbuilder</summary>
</details>
<details><summary>images/Dockerfile-sitebuilder</summary>
</details>
</blockquote>
</details>
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
- `gitlab-registry.cern.ch/paas-tools/openshift-client 4`
- `gitlab-registry.cern.ch/paas-tools/openshift-client 4`
- `mcr.microsoft.com/playwright v1.39.0-jammy`
- `mcr.microsoft.com/playwright v1.39.0-jammy`
- `gitlab-registry.cern.ch/paas-tools/openshift-client 4`
</details>
</blockquote>
</details>
<details><summary>npm</summary>
<blockquote>
<details><summary>playwright-test/package.json</summary>
- `@playwright/test ^1.39.0`
- `@types/node ^20.7.1`
</details>
</blockquote>
</details>https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/90Backup prior to deletion2024-03-27T00:05:01+01:00Carina AntunesBackup prior to deletionAutomate long lived backup prior deletion to allow easy recoveryAutomate long lived backup prior deletion to allow easy recoveryFrancisco Borges Aurindo BarrosFrancisco Borges Aurindo Barroshttps://gitlab.cern.ch/drupal/paas/renovate-bot/-/issues/1Dependency Dashboard2023-07-17T16:50:59+02:00Monica Jaqueline Iniguez MoncadaDependency DashboardThis issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detect...This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no open or pending branches.
## Detected dependencies
<details><summary>gitlabci</summary>
<blockquote>
<details><summary>.gitlab-ci.yml</summary>
</details>
</blockquote>
</details>https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/88Set lifecycle for Test projects2024-03-27T00:05:01+01:00Carina AntunesSet lifecycle for Test projectsSet lifecycle for 6 months and add section documenting to users.
Allow users to extend project life for 6 months max at each time.Set lifecycle for 6 months and add section documenting to users.
Allow users to extend project life for 6 months max at each time.https://gitlab.cern.ch/drupal/paas/cern-drupal-distribution/-/issues/17Add docker-compose for local development2024-03-27T00:05:01+01:00Carina AntunesAdd docker-compose for local developmentVineet Reddy RajulaFrancisco Borges Aurindo BarrosVineet Reddy Rajulahttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/87Fix deprecated Ginkgo functionality2023-01-24T15:53:07+01:00Vineet Reddy RajulaFix deprecated Ginkgo functionalityUnit tests have a warning due to deprecated Ginkgo funtionality
```
You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce (a small number of)...Unit tests have a warning due to deprecated Ginkgo funtionality
```
You're using deprecated Ginkgo functionality:
=============================================
Ginkgo 2.0 is under active development and will introduce (a small number of) breaking changes.
To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md
To comment, chime in at https://github.com/onsi/ginkgo/issues/711
You are passing a Done channel to a test node to test asynchronous behavior. This is deprecated in Ginkgo V2. Your test will run synchronously and the timeout will be ignored.
Learn more at: https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md#removed-async-testing
/home/rajula/Gitlab/drupalsite-operator/controllers/suite_test.go:69
You are using a custom reporter. Support for custom reporters will likely be removed in V2. Most users were using them to generate junit or teamcity reports and this functionality will be merged into the core reporter. In addition, Ginkgo 2.0 will support emitting a JSON-formatted report that users can then manipulate to generate custom reports.
If this change will be impactful to you please leave a comment on https://github.com/onsi/ginkgo/issues/711
Learn more at: https://github.com/onsi/ginkgo/blob/v2/docs/MIGRATING_TO_V2.md#removed-custom-reporters
To silence deprecations that can be silenced set the following environment variable:
ACK_GINKGO_DEPRECATIONS=1.16.4
```https://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/86Update unit testing suite to 1.242023-01-24T15:51:50+01:00Vineet Reddy RajulaUpdate unit testing suite to 1.24The unit tests suite is currently running on 1.21.4 and doesn't reflect our actual server versionThe unit tests suite is currently running on 1.21.4 and doesn't reflect our actual server versionhttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/85Set lifecycle for clones2024-03-27T00:05:01+01:00Carina AntunesSet lifecycle for clonesSet lifecycle for clones, eg 3 or 6 months and add section documenting to usersSet lifecycle for clones, eg 3 or 6 months and add section documenting to usershttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/84Extend automatic backup creation to 6 months2024-03-27T00:05:01+01:00Carina AntunesExtend automatic backup creation to 6 monthsExtend backup creation and add section documenting to usersExtend backup creation and add section documenting to usersFrancisco Borges Aurindo BarrosFrancisco Borges Aurindo Barroshttps://gitlab.cern.ch/drupal/paas/drupalsite-operator/-/issues/83Operator not updating image in specific situations2022-12-09T11:53:20+01:00Francisco Borges Aurindo BarrosOperator not updating image in specific situationsThe image version set on the `drupalsite` is not being set to the deployment.
This behavior occurs when there is no `failSafe` set on the status of the resource.
Example: `en-php8-preview`.The image version set on the `drupalsite` is not being set to the deployment.
This behavior occurs when there is no `failSafe` set on the status of the resource.
Example: `en-php8-preview`.https://gitlab.cern.ch/drupal/paas/cern-drupal-distribution/-/issues/13Module erros with testing PHP 82023-02-02T09:28:44+01:00Vineet Reddy RajulaModule erros with testing PHP 8```
[error] (Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 9.4.7:
* Date Popup
``````
[error] (Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 9.4.7:
* Date Popup
```