Umbraco 13.3.2: DeliveryContentAPI Examine Index created even if DeliveryContentAPI not enabled

[RachBreeze]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

Umbraco 13.3.2

Bug summary

If the DeliveryContentAPI is not enabled, the DeliveryContentAPI examine index should not be created this is for two reasons:

• Sustainability, we're using disk space (even tho it's small) for an index that wont be populated
• But more importantly, for people using ExamineX with Azure AI Search where Azure has a limit of 50 indexes every index counts, and this could tip sites over the edge for people trying to keep costs down on Azure AI Search hosting and use one Azure AI Instance for dev, test, uat and prod for example, or for sites that have a lot of examine indexes.

PS it would be great when looking at this if you could find away to disable the MemberIndex OOB for the same reasons.

Specifics

No response

Steps to reproduce

Install Umbraco 13.3.2, don't enable the DeliveryContentAPI

Expected result / actual result

No response

[github-actions[bot]]

Hi there @RachBreeze!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

Thanks @RachBreeze to report this. It is fair to say this is a feature request, and we like the idea, but it will require we rebuild the index when the delivery API is enabled. So it is not an easy fix. I will transfer it to a discussion.

[Matthew-Wise]

The API been enabled would trigger a site reboot wouldn't it? Meaning the index would be created on start up as it is now?

[RachBreeze]

Hi @NguyenThuyLan

@Shazwazza had thought of this for ExamineX https://examinex.online/configuration see "Disabling Specific Indexes". So it's not an issue for an ExamineX integration, but it would be good if Umbraco Core could do something similar with all indexes, every little helps as that famous advert goes :-)