Blocking overridding some variables via CLI

[narsdk]

Is it possible to mark specific test variables as immutable so that they cannot be overridden by CLI inputs (e.g. via --variable)? For example, I’d like certain configuration values to always use the value defined in the Test CRD or from an immutable ConfigMap/Secret. Overwriting these variables may cause security issues in my case (like running tests producing higher impact on environment than it is acceptable).

Any suggestions or plans to support this feature?

[vsukhin]

hey, @narsdk Test CRDs have been deprecated for almost a year and we are not actively developing features for them, only commong stuff like Test Triggers or Webhooks, still they are available. All the feaatires are developed for Test Workflows nowadays instead. Did you consider to try them out?