There seem to be a number of problems with default entities in code:
- After initial import, the status of servers and indexes will be "overridden".
- Reverting sometimes doesn't work, and never changes the "overridden" status.
- When reverting a server, all associated indexes are disabled and moved from the server (as the module thinks, the server is being deleted).
- Maybe problems when reverting an index, too? (Entries from {search_api_item} might be deleted.)
- Importing facets sometimes doesn't work (but maybe just because of problems with the index).

Comments

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented

Most of the bugs should be fixed now, for the rest see #1043634: Don't delete and re-create entities when they are reverted.
Leaving this open for now, until the above issue is fixed, or I know I have to work around this in the Search API.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Status: Active » Fixed

After some discussion in the Entity API issue and in person, we came to the conclusion that the current approach does make sense — both generally in the Entity API and in the Search API use case.
The alternative might be more user-friendly when reverting changes on a live server, but then again: on a live server, the configuration shouldn't be touched anyways.

Therefore, setting this to fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.