Bug: Error on SBOM import

[bdougie]

Describe the bug

When building an SBOM for nasa/open. Because I am importing for an SBOM, there 70+ repos and no indication of what is failing.

Failed on "eslint-plugin-no-unsanitized/issues"

Steps to reproduce

1. Add a repository insight
2. Import SBOM using "nasa/openmct"
3. Hit create and confirm the error.

My suggestion is skipping the repos that error and let the user know it was skipped, but allow the insight to be created.

The insight does get created despite the error, and filled with unrelated repos. Note the three instances of them while I was trying to triage.

[github-actions]

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue.

For full info on how to contribute, please check out our contributors guide.

[bdougie]

I can't delete an insight without upgrading as well. This is a dark pattern, that we will need to update as well.

When I click upgrade, I don't see delete. That might be annoying users.

[zeucapua]

re: @bdougie

When clicking the upgrade from the modal, it takes you to the workspace settings since it has the option, not the repository insight settings. The fact that the insight settings are gated behind an upgrade is confusing via the UI. You can get around this by changing the URL directly from .../dashboard to .../edit to get to the settings.

• Should I make an issue to only block the 'Update Workspace' button on the insight's settings rather than gating the page altogether?

• Are there options below that aren't allowed for non-upgraded users if the insight/workspace is above the limit? Eg. Users shouldn't be able to edit the repositories on creation if over the limit?

[brandonroberts]

I'll get a fix in on the API side for the repository import. The repository URL for the one that caused the failure is https://github.com/mozilla/eslint-plugin-no-unsanitized/issues

[brandonroberts]

@zeucapua Yea, they should be able to edit the repository insight if only to be able to delete it even if they are over the overall repository limit.

[brandonroberts]

Fixed parsing of the repository full names in the API for SBOM generation