Is your issue about flow object versioning or object storage file/data versioning or flow code versioning in general?
• Prefect automatically versions your
flows - anytime you register a flow, Prefect will bump up the flow version, as long as flow metadata changes. For more nuances about that, check
https://discourse.prefect.io/t/when-do-i-need-to-reregister-my-flow-which-changes-in-flow-metadata-result-in-prefect-bumping-up-the-flow-version/403
• For versioning of
flow code, you can commit your flow code to a git repo.
• For versioning of
files/data, you can turn on versioning on your S3 bucket which can help with disaster recovery and troubleshooting
Not sure if this is helpful to you, but I thought looking at versioning in those categories can be helpful
regarding upload on registration - yes - if you set key and local_script_path, Prefect will upload this local file to the given S3 key (path) during registration - see e.g.
this simple example
Registering new version of dataflow still increases version in UI,
The Discourse topic shows how you can avoid that