`circleci orb validate` fails with private dependent orb from same namespace
jschwanz opened this issue · comments
Meta:
CircleCI CLI Version:
- using image circleci/circleci-cli@sha256:eee9b00ad8929a528171d773e2ffc9d9f82fcd31c2e89a3da9f22bf17bf54bfc
- 0.1.19666+830e7ff (release)
Operating System:
Ubuntu 20.04
Current behavior:
I'm attempting to author a private orb that has a dependency on another private orb in the same namespace. When circleci orb validate runs as a part of orb-tools I get:
Error: Cannot find my-namespace/dep-orb@1.2.3 in the orb registry. Check that the namespace, orb name and version are correct.
Expected behavior:
I expect the orb validate process to be able to validate the use of private orbs from the same namespace.
This functionality already exists in circleci config validate with the --org-id and --org-slug arguments. It would be really nice to have it here, too.
Unfortunatelly I'm having the same problem.
Waiting for a solution
We are having this problem with our orbs as well. Effectively, it means we can't really use the circleci orb validate command as most of our private orbs cross-reference each other now for ease of maintenance/encapsulation/reuse.
Is there any update on this issue?
After the security breach we experienced in CircleCI we migrated to private orbs and are now blocked by this.
thank you for your sharing folks!
I am tagging our developer experience team here @CircleCI-Public/developer-experience to see if we can offer any updates on this 🙏
?
Thank you @kelvintaywl for your support on this issue. Hopefully the developer-experience team will find time to update this.
Hello,
Developer from @CircleCI-Public/developer-experience , really sorry we took so much time to answer. We are starting looking into the problem. @jschwanz, the solution we are going to make will surely look something like this but we first need our back-end to support this so unfortunately it's going to take a bit more time.
Anyway we are looking into the issue and we should fix it soon
Thanks for the feedback @JulesFaucherre. Has there been any progress on this. Running into this is quite tedious to get around and I am sure fixing it would uplift how companies can adopt and use Orbs more easily.
Hello, yes sorry for not getting back to this before! This took us a bit more time than expected because we had dependencies on other teams. Now it's a bit more advanced and we should be releasing this fix by the beginning of next week!
I've opened a pull request to solve this problem: #922
The orb validate will be able to accept org-slug and/or org-id flags just like config validate command.
Hello again ! The PR has been merged and a new cli version has been released fixing this issue (https://github.com/CircleCI-Public/circleci-cli/releases/tag/v0.1.26255)
Thanks to everyone who participated in this issue !