Motivation
The current naming approach for Cloud Security Transforms which includes the most recent version the Transform was edited, has the potential to confuse users.
For instance, individuals using version 8.10.0 might be confused when they encounter a Transform labeled "cloud_security_posture.findings_latest-default-8.8.0" on the Transform page.
This scenario is exemplified here.
The goal of this issue is to define different versioning method.
Motivation The current naming approach for Cloud Security Transforms which includes the most recent version the Transform was edited, has the potential to confuse users. For instance, individuals using version 8.10.0 might be confused when they encounter a Transform labeled "cloud_security_posture.findings_latest-default-8.8.0" on the Transform page. This scenario is exemplified here.
The goal of this issue is to define different versioning method.