📜 Deion I am attempting to follow the migration guide for t

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

🐛 Bug Report: `legacyPlugins` unreachable when migrating to 1.25 about backstage HOT 3 CLOSED

mspiegel31 commented on May 30, 2024

🐛 Bug Report: `legacyPlugins` unreachable when migrating to 1.25

from backstage.

Comments (3)

mspiegel31 commented on May 30, 2024 1

@Rugvip ahh, found the issue. I had forgotten to migrate the permissions backend as well. I needed to add the lines

// permissions + permission policy
backend.add(import('@backstage/plugin-permission-backend/alpha'));
backend.add(
  import('@internal/plugin-custom-permissions-backend'),
);

and now things are working as expected. Sorry for the noise, closing!

from backstage.

Rugvip commented on May 30, 2024

Do you have a backend.start() as well at the end? Could be what's missing although I wouldn't really expect it given the error. Looks alright otherwise though

from backstage.

mspiegel31 commented on May 30, 2024

Do you have a backend.start() as well at the end? Could be what's missing although I wouldn't really expect it given the error. Looks alright otherwise though

@Rugvip yup, there's a backend.start() call right after all the backend.add(...) statements.

does the new built-in authentication middleware return 404s when the request isn't authenticated? I get this response when trying to hit the backend API route through the terminal:

$ http --body http://localhost:7007/api/catalog/entities                                                                                                                                ue1.staging-ue1.staging
{
    "error": {
        "body": {
            "error": {
                "message": "Request failed with status 404 Not Found",
                "name": "Error"
            },
            "response": {
                "statusCode": 404
            }
        },
        "cause": {
            "message": "Request failed with status 404 Not Found",
            "name": "Error"
        },
        "message": "Request failed with 404 Not Found",
        "name": "ResponseError",
        "response": {
            "size": 0,
            "timeout": 0
        },
        "stack": "ResponseError: Request failed with 404 Not Found
          at Function.fromResponse (/Users/michaelspiegel/development/production/back-of-house/node_modules/@backstage/errors/src/errors/ResponseError.ts:76:12)
          at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
          at PermissionClient.makeRequest (/Users/michaelspiegel/development/production/back-of-house/node_modules/@backstage/plugin-permission-common/src/PermissionClient.ts:160:13)
          at AuthorizedEntitiesCatalog.entities (/Users/michaelspiegel/development/production/back-of-house/node_modules/@backstage/plugin-catalog-backend/src/service/AuthorizedEntitiesCatalog.ts:55:7)
          at <anonymous> (/Users/michaelspiegel/development/production/back-of-house/node_modules/@backstage/plugin-catalog-backend/src/service/createRouter.ts:135:40)",
        "statusCode": 404,
        "statusText": "Not Found"
    },
    "request": {
        "method": "GET",
        "url": "/entities"
    },
    "response": {
        "statusCode": 404
    }
}

I have the dangerouslyDisableDefaultAuthPolicy: true set in my app-config.yaml

backend:
  # Used for enabling authentication, secret is shared by all backend plugins
  # See https://backstage.io/docs/auth/service-to-service-auth for
  # information on the format
  auth:
    dangerouslyDisableDefaultAuthPolicy: true

from backstage.

Recommend Projects