Perhaps 'for flytectl' is more clear in terms of intent here.
The thinking is that, just like yes you can use aws cli to create resources, it is much nicer to define infrastructure via terraform using the aws provider than attempt to create scripts that runs aws cli.
I see a similar logic applying to flytectl, in terms of how to declare creating flyte resources on a flyte cluster.