#2142 [Core feature] Flytectl should generate matchable attribute template files Issue created by katrogan Motivation: Why do you think this is important? The guidance from flytectl says that to update a matchable attribute, a user should get the attribute, have flytectl write it as a yaml file, update the yaml file and then use the flytectl update command with the filepath as an arg. For example: https://github.com/flyteorg/flytectl/blob/master/cmd/update/matchable_plugin_override.go#L17 This leads to problems where no existing matchable attribute exists. Because the update API is an upsert, creating a matchable attribute in the first place becomes very difficult. Requiring users to know the protobuf structure in order to hand generate a yaml file is undesirable. It would be much simpler if flytectl could generate a template file that a user could modify and then pass to the update command. Goal: What should the final outcome look like, ideally? It should be simple to create a matchable attribute to pass when calling flytectl update Describe alternatives you've considered current implementation Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte