When trying to publish an orb that relies on another private orb, the publish job (as well as the CLI) will not allow the orb to be published as it will error on not being able to locate the orb in the orb registry.
Orb declaration (start)
version: 2.1
description: |
Example orb that depends on another internal orb
orbs:
orb1: private_namespace/orb1@1.0.0
Trying to publish the orb after its been packed results in an error. (Note: I have replaced the private info here. The new orb is just an update to an already private orb that has already been published).
Once an orb is created it cannot be deleted. Orbs are semver compliant, and each published version is immutable. Publicly released orbs are potential dependencies for other projects.
Therefore, allowing orb deletion would make users susceptible to unexpected loss of functionality.
Error: Cannot find private_namespace/orb1@1.0.0 in the orb registry. Check that the namespace, orb name and version are correct
Expected behavior:
It should utilize the token that is being passed to find the referenced orb and publish it successfully.
Orb version:
12.0.4
What happened:
When trying to publish an orb that relies on another private orb, the publish job (as well as the CLI) will not allow the orb to be published as it will error on not being able to locate the orb in the orb registry.
Orb declaration (start)
Trying to publish the orb after its been packed results in an error. (Note: I have replaced the private info here. The new orb is just an update to an already private orb that has already been published).
Expected behavior:
It should utilize the token that is being passed to find the referenced orb and publish it successfully.