error: An organization slug is required (provide with --org) #60
Comments
|
Hey @rimlin, per docs https://docs.sentry.io/learn/cli/configuration/
Therefore your config should look like this: [defaults]
url = https://sentry.io/
org = <org slug>
project = <project>
[auth]
token = <token> |
|
@kamilogorek thanks for reply, changed my config to INI standart and renamed it to So, i think what plugin could not find the config and use env variables, therefore i copied this config to project root and catch this error: Execution in project root Config file: Plugin usage: I tried to debug some info, but plugin nothing print except error |
|
Hmm... To verify this, you can use either Also, can you verify what |
|
I'm having a similar error. First it was related with wrong The token is from What I get is: @kamilogorek Any ideas what I did wrong 😞 ? |
|
@kamilogorek so, i could send sourcemaps to sentry, but for this i set my env varaibles SENTRY_ORG and SENTRY_PROJECT, because every time catch error: Command: |
|
@rimlin I had this issue and changing the name from |
|
Closing due to inactivity. Feel free to reopen if still relevant. |
|
@tavurth, where exactly do you insist to change the name ? Can you please provide the steps? |
|
In my [defaults]
url = https://our-custom-sentry-url.com
org = sentry
project = project-name
[auth]
token = our-sentry-token |
|
How the .sentryclirc file will created? |
|
You create it yourself from scratch |
|
You can use |
|
I have the same error. I try to run |
|
@pckhoi there's no project with a name |
|
Why config file is required? Is possible to overcome this programmatically? And have settings explicitly in the webpack plugin declaration |
|
It's not. See https://docs.sentry.io/cli/configuration/#configuration-values |
|
I've been messing with this for about an hour and still can't get the webpack plugin to not throw an error. Currently I'm getting: Here's how the plugin is called: My When I run Not doing any self hosting, this is all on sentry.io. Webpack config file and sentry cli config file are at in the same directory. Using @sentry/webpack-plugin Any insights? Thanks! |
|
@jketcham there's open PR fixing this getsentry/sentry-cli#700 (comment) :) |
|
Hello @kamilogorek ! I see the PR has been merged. Do you know when is going to be available for the next release? I just grabbed webpack-plugin from using npm and I still have 1.10.0. I am just asking because it seems that my config file is not found properly even though I specify configFile option in the plugin. Thank you in advance and regards |
|
@javierguzman bumped all the versions. Can you retry? |
|
Hello @kamilogorek Still the same :( I have the following configuration: configPath is the folder where the config file is. |
|
@javierguzman oh, that's |
|
@kamilogorek I think I am confused; My sentryclirc has the following format: As far as I saw in the exact link you sent, this is the correct way, isn´t? |
|
@javierguzman not really 😅 From README:
So your properties file should be: |
|
@kamilogorek My bad, thanks!! I am getting now an API request failure but I will investigate that further before I ask around, but that error means that at least now the configuration is grabbed ok! |
Yes, you can do it this way.
The difference between these two formats/concepts, is that properties file can live anywhere and be configured using |
|
@kamilogorek All clear then! At the very beginning I thought I could use .sentryclirc in the same way as the properties file that is why I even specified that in my webpack plugin configFile param. Now I have only a configSentry.properties file and that is. Thank you very much for your help Kamil. |
|
Anytime! Glad I could help. Cheers |
|
how to get org config? |
|
For others where the solution posted here didn't work, my CEO changed the org id and didn't tell me, check the org id you are passing in the .properties file is actually still correct! |
|
@AdamDiament man, you just saved my day! This was the exact issue I've run into |
|
I also stranded here whilst trying to figure what was going wrong with my sentry source map uploads. To debug my events that weren't matched, I was using the sentry-cli like so;
So I was searching how I could add the organization slug to my source map uploads. But this error wasn't about the event, but for using the explain CLI functionality itself!!! Which confused me. I had to pass additional parameters to the CLI script to get the actual problem with the event;
Maybe this will help someone else who also skipped over the docs 😅 |
|
For people who found the instructions for the CI/CD. This is how I changed the example to make it work. I know this is not a webpack issue but CI/CD or CLI. But people with problems with the CLI might end up here as well, just like me. curl -sL https://sentry.io/get-cli/ | SENTRY_CLI_VERSION="2.2.0" bash
SENTRY_AUTH_TOKEN=my-auth-token
SENTRY_ORG=my-organization
SENTRY_PROJECT=my-project
VERSION="v0.0.0"
sentry-cli releases new "$VERSION" --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --auth-token "$SENTRY_AUTH_TOKEN"
sentry-cli releases set-commits "$VERSION" --auto --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --auth-token "$SENTRY_AUTH_TOKEN"
sentry-cli releases finalize "$VERSION" --org "$SENTRY_ORG" --project "$SENTRY_PROJECT" --auth-token "$SENTRY_AUTH_TOKEN" |
Hi, trying to upload sourcemap to sentry, but catch this error:
There is how i use plugin:
And there is
sentry.propertiesfile:Tryed to set env variable directly (
export SENTRY_ORG= <org slug>) and run webpack again, but catch new error:Version:
"@sentry/webpack-plugin": "^1.5.2",The text was updated successfully, but these errors were encountered: