# Cylc validate doesn't test suite config against metadata?

**URL:** <https://cylc.discourse.group/t/cylc-validate-doesnt-test-suite-config-against-metadata/948>\
**Category:** Rose Support\
**Created:** [May 3, 2024, 2:38pm UTC](https://cylc.discourse.group/t/cylc-validate-doesnt-test-suite-config-against-metadata/948 "2024-05-03T14:38:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elliotfontaine](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/elliotfontaine/32/380_2.png) [@elliotfontaine](https://cylc.discourse.group/u/elliotfontaine)\
**Post date:** [May 3, 2024, 2:38pm UTC](https://cylc.discourse.group/t/cylc-validate-doesnt-test-suite-config-against-metadata/948/1 "2024-05-03T14:38:46Z")

</div>

The command `cylc validate .` doesn’t check the compliance of templates variables in `rose-suite.conf` against their metadata schema, the way `rose macro -V` would.

Is that expected behavior?

I figured I could create a R1 task doing `rose macro -V`, to do the job, but this could have its own issues since the validation is only done at runtime.

---

<div class="post-metadata">

**Author:** ![dpmatthews](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/dpmatthews/32/26_2.png) [@dpmatthews](https://cylc.discourse.group/u/dpmatthews)\
**Post date:** [May 3, 2024, 4:49pm UTC](https://cylc.discourse.group/t/cylc-validate-doesnt-test-suite-config-against-metadata/948/2 "2024-05-03T16:49:41Z")

</div>

Yes, this is expected at the moment (and note that `rose suite-run` never did this either). We have an issue to consider adding support for this: [https://github.com/cylc/cylc-rose/issues/23](https://github.com/cylc/cylc-rose/issues/23)