Choose how to get the data to audit

Created on 12 December 2022, about 2 years ago
Updated 28 June 2023, over 1 year ago

Problem/Motivation

In some cases, the audit is over an old project to know how is built and with that information take the decision to create a new project or refactor the current one.
The audit should be possible to do from different databases and Drupal versions.
Maybe also other CMS like Wordpress, Joomla...

Proposed resolution

Add the ability to choose the database and the Drupal version to get the relevant information from it.

Feature request
Status

Active

Version

1.1

Component

Code

Created by

🇪🇸Spain eduardo morales alberti Spain, 🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇪🇸Spain tunic Madrid

    The idea would be to have module installed in a Drupal site, where you can have the interface and results, but be able to run the queries on a set of tables of a different Drupal site, even a different software like Joomla, right?

    As long as it used SQL queries it should be feasible, but the configuration needs to change. We could add a configuration to select the target, or even allow multiple targets so the set of reports will be grouped on each target.

    I think the module is in a early stage to do this, but we should take this into account so when we are able to do this the module architecture is compatible with this idea.

  • 🇪🇸Spain lpeidro Madrid

    Hello:

    I thing the suggestion done by Eduardo it is to be able to audit older instances of a Drupal system, for example, for a migration from Drupal 7 to Drupal 9.

    The possibility to access to the old data base to get reports about data architecture from a new instillation.

    Here there are two points:

    • There are some features that should not be enabled in this case of use.
    • We have to adapt the queries for older version of Drupal. Here, one of colleagues suggested to study the migrate module to learn how to do it.

    But, how you say, @tunic, the module is in a early stage to do this, but this feature sounds very interesting.

  • 🇪🇸Spain GeduR

    I suggest facing this in multiple steps, the first one will be to be able to select the database (when there are multiple configured on the settings file), I imagine something like a select field on the top.

    In the first approach I will suggest to cover only the same version of Drupal the module is covering right now, so we can cover things like:

    - Migrations from D8 to D9 or D10
    - Migrations from other Drupal sites (d8-d10), that wants to be merged or checked
    - Remote instances databases
    - Multisite sites where I want to see other sites from one instance

    Note there are just examples of just allowing selecting the database and supporting the same version it helps in several use cases.

    Next steps will be to progressively support other Drupal versions and even other CMS (new specific issues)

    What do you think?

Production build 0.71.5 2024