Hey @TimNapier - any chance you’ve solved or worked around this yet? I’m having the same issue.
I’ve double-checked the Account prerequisite documented here, including validating in GitHub my connection configuration per this.
I’m using the syntax
packages:
- private: my-org/my-repo
and have tried with and without the provider key (even though I only have one integration configured on the account). Same with warn-unpinned (even though I don’t think it’s relevant in this case). I also tried quoting values, which has made no difference.
The package I’m trying to configure happens to be another project in the same dbt Cloud account and connected to another repo in the same GitHub org. There’s been no problem with authentication of that project from the Cloud interface, including development via the Cloud IDE. This particular project really should be installed as a native private package, but for the sake of due diligence, I also tried configuring it as a dependent project instead. Unfortunately, Cloud has been reporting a server failure for the past hour, and I’ve not been able to submit a dbt deps command since reconfiguring. I’ll update here if that turns out to be a workaround.
I have exactly the same issue as the op and want to avoid using tokens. GitHub is configure correctly as far as I can tell, we have multiple projects using different repos in the same tenancy without issue, now want to centralise our management of common macros in a separate repo but get the Private Package Org my_company_name not configured error when trying to refer to the repo using the private syntax.