Torizon repository sharing

Technical Support
, ,
2

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

Did you like my answer?

:+1: :-1:

Thank you for reaching out with your questions regarding Torizon repository sharing. Let’s address each of your concerns:

Issue 1: Credentials Tab Greyed Out

If the Credentials tab is greyed out for developers with “Full Access,” it might be due to a couple of reasons:

  1. Permissions Propagation Delay: Sometimes, changes in permissions might take a little while to propagate. Ensure that the changes have been saved and give it some time.
  2. Account-Specific Restrictions: There might be account-specific restrictions or issues. Double-check the Guest Profile settings to ensure that “Full Access” is correctly assigned.

If the issue persists, it might be a bug or a specific restriction in the system. In such a case, I recommend reaching out to Toradex support directly for a more in-depth investigation.

Issue 2: Pushing Images or Docker-Compose to the Company’s Repository

Developers can push images or docker-compose files to the company’s repository using their own credentials. Here’s how you can manage this:

  1. Using Personal Credentials: Developers can use their own Torizon Cloud credentials to push updates to the shared repository. They do not need to share the company’s credentials.zip file. Each developer should have their own credentials set up in Torizon Cloud.

  2. Repository Access: Ensure that the developers have the appropriate access level to the repository. “Full Access” should allow them to push images and docker-compose files.

  3. TorizonCore Builder Tool: Developers can use the TorizonCore Builder Tool to authenticate and push updates. They should follow the steps to authenticate with their own credentials and then push the updates to the shared repository.

If you need detailed steps on how to push updates using the TorizonCore Builder Tool, you can refer to the TorizonCore Builder Tool documentation.

Summary

  • Ensure that the “Full Access” permissions are correctly assigned and propagated.
  • Developers should use their own Torizon Cloud credentials to push updates.
  • Refer to the TorizonCore Builder Tool documentation for detailed steps on pushing updates.

If you continue to face issues, please contact Toradex support for further assistance.

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

Issue building and running Containerized TorizonCore Build on MacOS.