Hi everyone Quick question is the ` force` flag on `flytectl

Question

Hi everyone Quick question is the ` force` flag on `flytectl register files` working When I use it the CLI logs AlreadyExists which makes it look like it didn t actually rewrite anything Is this normal If so shouldn t the logs print another message such as Overwritten or something I m using FlyteCTL 0 5 6 by the way

Yee · Answer

not quite sure i understand i didn t think there was a force flag

Yee · Answer

` files force`

Yee · Answer

i don t think that s what that means maybe < Prafulla Mahindrakar> can clarify when he gets back on tonight Flyte admin will never overwrite something like that at least it s certainly not supposed to

Yee · Answer

immutable

Matheus Moreno · Answer

No apparently there s a force flag specifically for register flles

Matheus Moreno · Answer

Matheus Moreno · Answer

``` force Force use of version number on entities registered with flyte ```

Yee · Answer

what that flag might be for is that it will ignore the version that s in the files

Yee · Answer

and use what you pass it instead

Matheus Moreno · Answer

ohhh ok that makes sense

Yee · Answer

that is when you have a task pb that pb message is <https github com flyteorg flyteidl blob master protos flyteidl admin task proto L51>

Yee · Answer

which has a tasktemplate which has an id which has a version

Yee · Answer

yeah

Yee · Answer

i think

Prafulla Mahindrakar · Answer

force flag will just force to use the version passed in the command line params and not use what there in the serialized version of the file but that doesn t prevent admin from throwing an already exist error if the version being passed already exists As yee mentioned flyte objects are immutable So if you want to avoid getting ALreadyexists error then you would need to pass in a new version