Update Acquia Telemetry config path

Created on 20 December 2022, about 2 years ago
Updated 27 January 2023, almost 2 years ago

Problem/Motivation

When upgrading from 3.0.5 to 4.0.1, the following post update hooks run:

 ------------------ --------------- ------------- -------------------------- 
  Module             Update ID       Type          Description               
 ------------------ --------------- ------------- -------------------------- 
  acquia_connector   deprecated_va   post-update   Rebuild a simple acquia   
                     riables                       connector config object.  
  acquia_connector   migrate_acqui   post-update   Migrate acquia telemetry  
                     a_telemetry                   settings to connector.    
 ------------------ --------------- ------------- -------------------------- 

acquia_connector_post_update_deprecated_variables appears to remove the spi key from configuration, which makes sense because I no longer see spi in the schema.

But then acquia_connector_post_update_migrate_acquia_telemetry comes along and sets spi:

$acquia_connector_config->set('spi.amplitude_api_key', $api_key);

The net result is that my acquia_connector.settings.yml has a value for spi.

Is that the intended result? Or are the post_update hooks supposed to run in the opposite order? Or is the schema wrong?

I originally had this as a support request, but then decided there is at least one bug here: either the updates are wrong of the schema is wrong.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States danflanagan8 St. Louis, US

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.

Production build 0.71.5 2024