Using the CLI to validate a config that references a private orb

Feedback & Bug Reports
8

I had seen the notes about it not working at all, so this is a big improvement (being able to specify --org-slug)!. For me, this works great, and I’m now able to validate configs with private orbs.

That said, wonder if there’s any plan to add any further improvements, like letting you set an organization to search for private orgs by default?

for publishing, I see this config in cli.yml:

orb_publishing:
    default_namespace: ""
    default_vcs_provider: ""
    default_owner: ""

I tested, and populating these values (or setting org_slug there) did not seem to work, but it would be nice if the CLI config could either infer the slug from those fields in orb_publishing, or have a parallel field for validation.