-
Notifications
You must be signed in to change notification settings - Fork 11
Cannot read property 'length' of undefined #4
Comments
I wonder if the issue is here: backstage-plugin-jira/src/api/index.ts Line 27 in c71a684
This endpoint does not exist on Jira Server / Data Center. Even in the latest release, 8.14, it's This is the doco for the rest API in the latest release: https://docs.atlassian.com/software/jira/docs/api/REST/8.14.0/ And I'm on a slightly older 8.x from earlier this year which only has a But the cloud doco has the v3: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ So two fold:
|
@adamdmharvey Thanks Adam. We will investigate and come up with a few improvements. We'll keep you updated. |
I just created a PR: #5, hopeful it will resolve all reported issues. |
@adamdmharvey I just published new version of the plugin on the NPM (0.2.0). Please try the new version if you could and let me know if it is working.
|
This is fantastic, thanks @lewtakm - really appreciate your efforts here. So far, not able to get the
You'll see all of my testing is hitting the v3 API URL which I don't have on my Jira Data Center instance: Now, as a very odd test, I tried resetting the proxy config like so:
I can see this loading via the Backstage startup:
Which means I've successfully registered this proxy path. HOWEVER, it seems the plugin is still using the default proxyPath defined in the code:
So I'd almost wonder - perhaps none of the configuration options are being properly loaded into the plugin at all? Maybe a test case (a la Any advice? THANK YOU AGAIN! |
FYI cloning locally and manually replacing the |
I've further tested multiple times, and for the life of me can't get the options to load. I'm pretty confident neither the proxyPath from the actual config nor the apiVersion are being read in. However, the validations all work properly. (e.g., if changing the config schema and running I did find if I hardcode it here:
That works, so it's being passed around, but NOT being collected from the config API call. |
@adamdmharvey can you tell me if are able to read any others data from config? For example if you put console.log like this: Your config is printed correctly on the console? |
@lewtakm Interestingly, no. With the log on, tried both in Tried a few different placements in the location of the file as well. Assume it works for you? |
@adamdmharvey yes it works. My last thought can you confirm that you have configSchema in package.json file of the plugin? |
Going to mark this one closed! Re this thread: I had git cloned this repo, put it in my So maybe I'll report a bug in Backstage itself. Thanks Mateusz! |
Trying out the new plugin, but not able to get it to work yet. Various permutations, I keep getting this:
Also the resulting link for "Project ->" ends up just being the URL for my component with a suffix of my annotation project-ley (so it's reading that), i.e.
http://localhost:3000/catalog/default/component/adams-component/undefined/browse/PROJKEY
.I've tried a few different permutations of settings, restarting Backstage each time to confirm I'm picking up my
app-config.local.yaml
changes, including:target
beinghttps://mycustomJiraUrl.company.com
target
beinghttps://mycustomJiraUrl.company.com/api/2
(the REST API end point)Would be valuable maybe to...
LOG_LEVEL=debug
to the env vars, could this plugin pick them up?)Any help appreciated, and/or happy to try bug fixes/tweaks?
Thanks!
The text was updated successfully, but these errors were encountered: