Fredrik Adelöw

Is there no way that we can make this environment "pluggable" (maybe even at a per package level) so that people don't have to bump all of them at once?

The github providers have [a dedicated `githubOrg` config key](https://github.com/backstage/backstage/blob/6fc3b9f8fb1df313fa90ee7760a1d6d823c3abae/plugins/catalog-backend-module-github/config.d.ts#L218) separate from the file-based ones. Maybe that would have been nice for this provider too.

Note the warning above - you need to add a changeset to the PR.

> it appears that backstage by default sets its Referrer Policy to 'no-referrer' This is the default policy of the `helmet` middleware that's being [added by default](https://github.com/backstage/backstage/blob/ac5f3dfb95816f21ff8bfd7f9bbbf749a4b80e0c/packages/backend-defaults/src/entrypoints/rootHttpRouter/rootHttpRouterServiceFactory.ts#L189) to all routes....

Does this help? https://github.com/backstage/backstage/blob/master/contrib/docs/tutorials/help-im-behind-a-corporate-proxy.md

Let me just check one thing. The migrations intentionally destroy data, right? They find collections of rows where there are duplicates and destroys all but one of those rows. It...

@drodil also noting that it has a concurrency limiter - if generation can't keep up with demand, it'll probably pile up more and more pending generations, and whatever state they...

It'd be great if you had the chance to yarn-patch in a minimal change and just see the problem not reoccur - if you can

Pointing @squid-ney I think since I'm a bit out of my depth!

Thanks for writing this up. This could definitely make sense (whether in the core model or as an extension). Possibly in the form of a `kind: Environment` and some set...