-
Notifications
You must be signed in to change notification settings - Fork 82
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
Migration problems cannot generate protos any longer #1337
Comments
Looks like you are using a v2 If you are using local plugins, change Also just out of curiosity, was this working prior to running the migration tool? The migration tool makes changes to your plugins, but it should not change your version from v1 to v2. |
my bad the property name I did not change it, yes migration tool did not change v1 to v2 that was me doing it manually. now after updating buf to version 1.47.2 and trying to generate again I get this errors, don't know where to get connect-go and knit-ts since it was long ago I had all this running prior to upgrading, could you please help me on this?
|
With buf.gen.yaml v2, you need to specify I suggest to revert, and run Or keep buf.gen.yaml at v1 - you don't need to upgrade the config file, and can do that separately. |
If you want to use
As an alternative though, you can just use the remote plugins found on the BSR and you don't have to install anything locally. To do so, change |
Thank you so much for your help. All has been generated successfully. |
Just reopened as I was trying to use the plugins locally and when installing following the documentation on the links you provided me with I get these errors. Any light on them of what I'm doing wrong?
package.json has
buf.gen.yaml (local)
|
Hey! Are you trying to use both knit and connect? |
I followed all steps to migrate and I'm also using knit
npx @connectrpc/connect-migrate@latest
But I'm getting these errors when generating protos
npx buf generate
buf.gen.yaml
buf.yaml
Anybody can provide me with help?
The text was updated successfully, but these errors were encountered: