Error: repo.bat package with --name parameter

[InvdrSim]

Trying to package my app using the ./repo.bat package command.
Kit Version is 109.0.1, fresh from the git repository.

Command:

./repo.bat package -n "my_app"

Output:

The redirected argument -n to --image-tag has new behavior. If a value of image_name:version_string is provided, that will be used to build your container. If no colon is detected, your container’s tag will be application_name:the_value_of_this_argument

error: unrecognized arguments: --image-tag my_app

Same also happens with the --name parameter. Documentation suggests that --image-tag is a parameter for the package_container command instead. Seems like some preprocessing is happening here that should only be applied for that command, not for the package command.

Is this a bug, or am I missing something?

[Richard3D]

Please just use repo.bat package, without the -n and it will package the app directly. There is no need to direct it to the particular kit file.

[InvdrSim]

Found the error in repo.toml:

[[repo.deprecations]]
tool_name = "repo_package"
command = "package"
arg_name = "--name"
arg_redirect_name = "--image-tag"
log_message = "The redirected argument --name to --image-tag has new behavior. If a value of image_name:version_string is provided, that will be used to build your container. If no colon is detected, your container's tag will be application_name:the_value_of_this_argument"

As far as I can tell, tool_name really should be “repo_package_container” and command should be “package_container”.
Changing this makes the “package” command work with the --name parameter again.

I am not trying to direct it to a particular kit file, I am trying to give the package a name.

[Richard3D]

I see. Ok, well I am glad you found the command. It just zips it up anyway, so you can always just rename the zip file after it packages.

[InvdrSim]

True, but I am running this in a CI/CD pipeline, building 3 separate apps from one repo. I’d either have to add an addititonal step for the renaming or get confused as to which artifact is what. Fixing this deprecation/redirection seems to be the least amount of pain.

I think the confusion stems from the fact that the package_container command apparently used to be just the package command with the --container argument. The intention seems to give developers who were using this a clear way forward to using the new command, but this just broke the regular package command. As of right now, this part of the companion tutorial fails.

[Richard3D]

Thanks for flagging this. I asked the engineers and they said that the change was mentioned in the changelog.md that ships with the new version.