Upgrading module to version 8.3.0 from 8.2.2 causing some issue

Do not update existing solr configs. Sorry, this was changed for ci/testing purposes. Your current config should work. We had to start CI that tests the module on D10 & D11 for compatibility whereas before we were only testing on 9.

Bot in our existing index config we are using

dependencies:
  config:
    - search_api.server.pantheon_solr8
server: pantheon_solr

So as per the change in 8.3.1 version we need to update this to pantheon_search ?

If this change is done for CI/testing purpose then this search_api.index.primary.yml should belongs to a test module.
We didn't get this issue in 8.2.x because the yml file name is wrong search_api_index.content_index.yml. But in 8.3.x this yml file is corrected and we are getting below error On our local/CI instance where pantheon_search server is not available.

  [Drupal\search_api\SearchApiException]                                       
  The server with ID 'search_api_solr_drupal_server' could not be retrieved f  
  or index 'primary'. 

I'm seeing a similar problem in my project.

We have our own custom search module that installs its own index config in /config/install. This config is using the pantheon_solr8 server as defined in the last line of the config: server: pantheon_solr8.

The problem is, when we update the search_api_pantheon module to 8.3.x, we need to update that config via an update hook so the server line is now pantheon_search. The problem is, the pantheon_search server will not exist, because we aren't reinstalling search_api_pantheon. So this new /config/install/search_api.server.pantheon_search.yml file never gets installed.

For new sites we spin up and enable our custom search module on, then sure...when search_api_pantheon gets enabled, it will be for the first time, so the new pantheon_search server config will get installed. For our existing sites though, they will still be using the pantheon_solr8 server because there is nothing in the 8.3.x version of this module that will update that for us.

@stovak Perhaps that config should never have been renamed? If so, shouldn't there be something in an update hook that fixes this for us?

There are some more issue we are seeing.
Even if we update our index config to use updated server id "pantheon_search" we ended up with whole indexed data lost. and index is staged again for re-indexing