Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to publish a Orb if it depends on an internal private orb #228

Open
christopherbox opened this issue Sep 28, 2023 · 1 comment
Open
Labels
bug Something isn't working

Comments

@christopherbox
Copy link

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.
image

Orb declaration (start)

version: 2.1
description: |
  Example orb that depends on another internal orb
orbs:
  orb1: private_namespace/[email protected]

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/[email protected] 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.

@christopherbox christopherbox added the bug Something isn't working label Sep 28, 2023
@igordodt-nuvemshop
Copy link

Any update on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants