hello everyone, i was wondering if for a CI setup ...
# ask-community
s
hello everyone, i was wondering if for a CI setup if it is good, to not only make it register flows to ensure that the deployment reflects what is in code that way, but also when a flow is removed from the repo that it gets automatically deleted at prefect as well? or does this interact badly with how prefect is designed and the intended development workflow?
c
Hi sark, I think this makes sense! All of the API routes are exposed so that users can be creative with how they use them, and this use sounds reasonable to me
s
hi chris, sorry but what i meant was in this case it doesn’t seem to work well, because for example: • CI registers a new flow • the flow runs a few times • CI deregisters the flow because flow code was deleted • CI registers the flow again because the deletion was reverted with git • but the new flow now does not contain the flow runs corresponding to the first registration
c
I don’t think I understand what you’re hoping to change though - when you delete a flow, naturally all of its run history is also deleted; if you don’t want that to happen, maybe archiving the flow is a better fit for your use case