twanbeeren

We're facing the same issue right now. How do we upgrade an environment without upgrading other environments while using ApllicationSet

Still no update on this? It would be really helpful

Do you need to set a profile.email? Like so ``` apiVersion: backstage.io/v1alpha1 kind: User metadata: name: tbeeren spec: profile: displayName: TwanBeeren email: [email protected] memberOf: [guests] ``` Maybe this helps

Just to clarify here: It is only necessary to make changes in the app-config.yaml? My app-config.yaml ``` catalog: providers: microsoftGraphOrg: providerId: target: https://graph.microsoft.com/v1.0 authority: https://login.microsoftonline.com clientId: ${AZURE_CLIENT_ID} clientSecret: ${AZURE_CLIENT_SECRET} tenantId:...

I'm also facing similar issues and would like to share what I've done to resolve it to this point. Let's say that I'm not a hero (yet) with dockerfiles, and...

From what I know the latest Backstage version only supports node 20 and node 22 I resolved my comment from above by updating the OS image to node 20 and...

This issue also causes OOMkills for us. Temporary solution was to create a cronjob that restarts the operator every day so that it doesn't consume a lot of memory and...

Cronjob ``` apiVersion: batch/v1 kind: CronJob metadata: name: kill-ama-operator-cj namespace: kube-system spec: schedule: "0 6 * * *" # Runs every day at 6:00 AM jobTemplate: spec: template: spec: containers:...

After some googling I alsoagree that this might be a graph limitation instead of Backstage. I need to look if starts_with is also an option. I rather not use that,...

If there is no way to work around this I'm willing to close this ticket since it's not really a backstage issue