Thread
#prefect-community
    l

    Leo Kacenjar

    6 months ago
    Hi there, I'm trying to automate registering/updating flows via a Jenkins automation job. I pull and build our docker image, login via the cli and then attempt to register the flows. This is all working well. However every time I run this process, I get a new version for all of my flows even when nothing but the docker image id and container id has changed. Does it seem possible to not create these revisions or is this by design? I've tried registering with numerous versions of the command. Thanks!
    Kevin Kho

    Kevin Kho

    6 months ago
    What timing! Anna just wrote this about it. You can use the CLI because it won’t bump up the version by default
    l

    Leo Kacenjar

    6 months ago
    That is helpful and well timed. Thanks! I'm guessing that running register from inside ephemeral containers must be causing some of the flow metadata to change. However, I'm not sure which aspect of the metadata that would be.
    Kevin Kho

    Kevin Kho

    6 months ago
    The metadata is listed there at the bottom, but if you have stuff like
    datetime.datetime.now()
    or anything like that during build time (schedules or parameters), it can change the hash also
    l

    Leo Kacenjar

    6 months ago
    Ok, this gives me some stuff to dig into. Thanks!
    Jack Chang

    Jack Chang

    6 months ago
    Is there a maximum number of versions a flow can have? Like how there is a max 20,000 flow runs for free accounts
    Kevin Kho

    Kevin Kho

    6 months ago
    Not that I know of. Never heard of anything like it so I don’t think so