Change config object name from gemini_provider.settings to ai_provider_gemini.settings

Created on 12 February 2025, 2 months ago

Problem/Motivation

Almost all AI providers have the configuration object name in the same format ai_provider_<provider_name>.settings. It is not a big deal, that the config name in Gemini module is different, but in case of some automation when there are multiple providers involved, it would be nice to rely on the same naming convention.

Proposed resolution

Change config object name from gemini_provider.settings to ai_provider_gemini.settings to follow the pattern from all other AI providers.

Remaining tasks

Create MR with update hook

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany a.dmitriiev

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

Merge Requests

Comments & Activities

  • Issue created by @a.dmitriiev
  • Pipeline finished with Success
    2 months ago
    Total: 134s
    #422024
  • 🇷🇴Romania vasike Ramnicu Valcea

    Usually the module name is used for its settings/config name ... so not sure about changing the config name ...
    Maybe if this is something that it's expected by AI APIs.

    However this MR brings nice update to use CONSTant for the settings ...
    maybe we could have an interface .. GeminiProviderConfigInterface that could re-used in the module ...

    just saying

  • 🇩🇪Germany a.dmitriiev

    I agree that it might be too late to change, but as it is still alpha, maybe it is time now or never. It is of course too late to change the module name :)
    This issue purpose is a discussion first as it is not a requirement to follow AI module naming convention. So maybe this change is just "nice to have".

  • 🇬🇪Georgia jibla

    This is related to the module name.

    When I started the module, there was no naming convention at all, even all the existing providers where part of the AI module. I agree its better if the module is renamed to ai_provider_gemini.

    I am going to work on the renaming after we release this changes. After this I will see if its possible - we need to rename namespace in url/composer without affecting already installed instances. I will take care of this after this release, meanwhile I am setting this issue as postponed.

Production build 0.71.5 2024