[discussion] How to handle serverless project sub-types #1691
Description
Serverless project subtypes are proliferating. This is an open discussion to assess the need (or not) to include this is our tagging system, wether it's as part of the applies_to or something else.
Subtypes we have today:
- Elasticsearch (those are backend configs, they don't change the features available)
- Optimized for Vectors
- General purpose
- Optimized for Time Series (soon)
- Observability
- Complete
- Logs Essentials
- Security
- EASE (soon)
- Analytics Complete - with add-ons possible
- Analytics Essentials - with add-ons possible
For Obs and Security especially, these subtypes translate into actual feature differences, hence raising the question of possibly needing some tagging.
On the other hand, these feature tiers also feel like "subscription levels", which we don't document yet, and if we did, we'd probably want to also discuss how to handle that intelligently in our tagging (or not in our tagging).
At the moment, I don't feel like we should make our tagging more complex or go to that granularity with our current applies_to. But still opening the debate.
cc @elastic/docs-tech-leads