Use torizoncore-builder to add tags for torizon.io packages

[vix]

I know how to use torizoncore-builder (tcb) tu publish packages to torizon.io cloud.
In the cloud I see there are a lot of tags that helps me filtering the several packages

Is there a way to use tcb to specify which tag(s) I would like to be appended to the packge I’m going to publish?

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Based on the provided context, the torizoncore-builder (tcb) tool does not support specifying tags directly during the package publishing process. You will need to manage and append tags to your packages through the Torizon.io cloud interface after the packages have been published. For detailed instructions on managing tags, you may need to consult the Torizon.io documentation or support resources.

Please, also check if these links can help you solve your problem:

app.torizon.io says "Unable to initiate update"

I try to update firmware I have successfully update before. But recently it says “Unable to initiate update Please make sure the selected package is compatible with the selected device” my docker-compose.yml version: "2.4" services: weston: container_name: weston image: register/App-weston ... portainer: image: portainer/portainer:latest ... App-client: container_name: App-client image: register/App-client ... May be the problem is related…

TCB cannot do "platform push" if private docker registry.

[jeremias.tx]

Greetings @vix,

You can affect what tags do show, up though the interaction is a little unclear if you don’t know.

To explain, the list of tags you see is more or less a list of package names found in the package sources you have checked on the left.

So for example, on my account I have a package named hello-world, this leads to me having a tag of the same name. Another interaction here, is how package names with / characters are treated. When you have a package name like 6/apalis-imx8/torizon/torizon-core-docker/testing for example. Then every string separated by a / becomes it’s own tag. So with this example I would have the following tags produced by this single package name:

• 6
• apalis-imx8
• torizon
• torizon-core-docker
• testing

So yes in a way you can affect what tags are available via the names of your packages you have on your account.

Best Regards,
Jeremias

[vix]

@jeremias.tx

When you have a package name like 6/apalis-imx8/torizon/torizon-core-docker/testing for example. Then every string separated by a / becomes it’s own tag. So with this example I would have the following tags produced by this single package name:

• 6
• apalis-imx8
• torizon
• torizon-core-docker
• testing

Do you mean that this list of tags is added as “existing tags”, and the package is tagged with all the above tags?

[jeremias.tx]

Do you mean that this list of tags is added as “existing tags”, and the package is tagged with all the above tags?

Yes. But, again the available tags is based off of your current list of packages and their names. If you for example delete the 6/apalis-imx8/torizon/torizon-core-docker/testing package, and you have no other packages that provide the same tags, then these tags disappear from your list. Until you upload another package with similar tags.

Best Regards,
Jeremias