Fredrik Adelöw
Fredrik Adelöw
Hi! This has been asked for before but there are a few missing pieces. The scheduler is plugin scoped so its state is local to the plugin itself. It also...
No, the backend system in and of itself didn't implement that feature. It'll be nicer to build the feature upon that system, but no, it's not in place.
Oh we actively excluded that warning in e2e it seems https://github.com/backstage/backstage/pull/27286/files#diff-3eeadc52319d85819c5ae205a28df8ddf566c2ce9a60bedf3b75ae393864a1eeR535
Nice idea, but I'd like to call out two things: - This probably requires https://github.com/backstage/backstage/issues/24169, which was what blocked a previous attempt at getting rate limiting into place (it was...
Yeah it turns out that that setting is _REALLY_ important to get right, because without it, a lot of proxied use cases will just bundle all callers into one single...
Oh and also - need to rerun for the api reports which are named differently now.
rudely rebased on latest master and force pushed
Yeah that just got fixed https://github.com/backstage/backstage/pull/27153
Hi! Feel free to rebase this while waiting for us to get back up to speed.
Just popping by to note that I was going through old pull requests and saw this one. There are conflicts and actionable comments above still, right, am I understanding this...