#4762 [Core feature] Pyflyte 'task with different structure' should show delta Issue created by katrogan Motivation: Why do you think this is important? It's difficult as a user when I try to register Flyte inventory and get back

details: task with different structure already exists with id resource_type:TASK project:"system" domain:"production" name:"task-name" version:"1234"

but I can't tell what's changed in my local version of the task. Since we already store the registered task template and have the current serialized version of the task template we're trying to register, it would be super slick if flytekit (pyflyte) could compute what parameters in the template changed across registration and highlight that to the end user. (same for workflows and launch plans) Goal: What should the final outcome look like, ideally? Should be straightforward to identify what has changed across registration versions when the back-end blocks a re-registration attempt Describe alternatives you've considered Current error response code user experience Propose: Link/Inline OR Additional context Much like we use json marshalling to compute the hash, we could just json serialization to compute the delta here. No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte