Marco Crivellaro
Marco Crivellaro
@Irma12 having the option to completely remove the activity stream makes sense! Thanks
Hi, thanks for getting back to me, I thought that would have been the challenge. I had a look at using `backstage_resource` and `backstage_component` but they fetch a single entity...
thank for the update!
I think I can take a look, do you have a reference I can take a look at to see how to implement Backstage caching? Thanks!
Yeah it makes sense to cache that way, we just need to expire it. We ingest users using the GitHub Org Provider.
@jalseth updating the dependency solves the problem, however it introducing a list of changes that will break existing policies. I've opened a PR in my fork to demonstrate the impact...
We're run into the same issue since yesterday (07 Oct 2025). The issue is occurring with versions v0.65.0 to v0.67.0. The issue is not present in v0.64.1 Versions from v0.65.0...
I just wanted to inform you that the issue isn't happening anymore. I've tested against the configuration of my first example and there are no hits for `storage-bucket-versioning-disabled` rule