Removed deprecation warning about backend.auth.keys

[04kash]

Description of the change

Fixed default configuration to remove deprecation warning about backend.auth.keys by replacing it with https://github.com/backstage/backstage/blob/master/beps/0007-auth-external-services/README.md#the-legacy-access-type

Existing or Associated Issue(s)

Fixes: https://issues.redhat.com/browse/RHIDP-2716

Additional Information

Checklist

• Chart version bumped in Chart.yaml according to semver.
• Variables are documented in the values.yaml and added to the README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes.
• JSON Schema template updated and re-generated the raw schema via pre-commit hook.
• List tests pass for Chart using the Chart Testing tool and the ct lint command.

[coreydaley]

I think that you also need to run the pre-commit hook to regenerate the schema and update the README

[rm3l]

/cc @rm3l

Planned for 1.2.2. See reasons in https://issues.redhat.com/browse/RHIDP-2716?focusedId=25057410&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-25057410

[openshift-cherrypick-robot]

@rm3l: once the present PR merges, I will cherry-pick it on top of 1.2.x in a new PR and assign it to you.

In response to this:

/cc @rm3l
/cherry-pick 1.2.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[rm3l]

Works fine - thanks @04kash !! For the reasons mentioned in https://issues.redhat.com/browse/RHIDP-2716?focusedId=25057410&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25057410, this PR should not be cherry-picked to 1.2.x.

[rm3l]

Tests not passing because the latest tag for quay.io/janus-idp/backstage-showcase is outdated, and the changes here won't work on RHDH 1.1

Logs

/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1481
          throw new Error(
                ^

Error: Failed to instantiate service 'core.tokenManager' for 'search' because the factory function threw an error, Error: Failed to instantiate service 'core.tokenManager' because createRootContext threw an error, Error: You must configure at least one key in backend.auth.keys for production.
    at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1481:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async BackendInitializer.getInitDeps_fn (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1644:20)
    at async /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1779:32
    at async processNode (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1302:22)
    at async Promise.all (index 0)
    at async processMoreNodes (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1297:7)
    at async _DependencyGraph.parallelTopologicalTraversal (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1308:5)
    at async /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1777:9
    at async Promise.all (index 4)
    at async BackendInitializer.doStart_fn (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1757:3)
    at async BackendInitializer.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1611:5)
    at async BackstageBackend.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1881:5)

Node.js v18.18.2

I think quay.io/janus-idp/backstage-showcase:latest should be updated to the latest stable version of the Showcase app.
See https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1720191475569659

/hold

[coreydaley]

@rm3l So do we need to change the image here to point to next instead?

[rm3l]

@rm3l So do we need to change the image here to point to next instead?

We discussed in https://redhat-internal.slack.com/archives/C04CUSD4JSG/p1720191475569659 (https://issues.redhat.com/browse/RHIDP-3157) that it would probably make more sense to use the downstream RHDH image here. next tag may be unstable to be used in the Helm/Operator PR tests.
@04kash Could you please update the image in values.yaml to use quay.io/rhdh/rhdh-hub-rhel9:latest instead of the outdated quay.io/janus-idp/backstage-showcase:latest ? The test should pass with the RHDH image..
I'm making similar change in the operator repo.

[coreydaley]

/hold cancel

[coreydaley]

/lgtm

[coreydaley]

/approve

[coreydaley]

@04kash Are you ready for us to merge this?

[04kash]

@04kash Are you ready for us to merge this?

Yes