fix(test): adds auth test key as auth is mandatory

[ChrisJBurns]

Description of the change

Authentication has been enabled by default in newer versions of Backstage. This adds a dummy secret so tests can continue as normal.

Existing or Associated Issue(s)

Fixes #186

[ChrisJBurns]

@vinzscam @tumido @sabre1041

Hi all, it seems that CI tests are failing now due to auth being enabled by default in the newer versions of Backstage. I've added a test secret just so we populate that value (even though in production users would add it via a secret)so the tests can continue. There is a weird couple of test scenarios whereby the auth.keys are only needed for two of the CI test values files we're using - which we may have to look into. Either way, it seems to have got past the auth.key issue now and onto a techdocs issue. Not sure if any of you have seen this recently? When I install in a local kind cluster I also get the same error.

ForwardedError: Plugin 'app' startup failed; caused by Error: Invalid app bundle schema. If this error is unexpected you need to run `yarn build` in the app. If that doesn't help you should make sure your config schema is correct and rebuild the app bundle again. Caused by the following schema error, Error: Config validation failed, Config must have required property 'techdocs' { missingProperty=techdocs } at 

Welcome your thoughts! If I can get this PR merged relatively quickly, there are some updates I want to make to the Postgres sub chart versions and contributing docs whilst I have time over the bank holiday here in the UK!

[sabre1041]

@ChrisJBurns I'll try to find time to test this out at some point this weekend

[vinzscam]

@vinzscam @tumido @sabre1041

Hi all, it seems that CI tests are failing now due to auth being enabled by default in the newer versions of Backstage. I've added a test secret just so we populate that value (even though in production users would add it via a secret)so the tests can continue. There is a weird couple of test scenarios whereby the auth.keys are only needed for two of the CI test values files we're using - which we may have to look into. Either way, it seems to have got past the auth.key issue now and onto a techdocs issue. Not sure if any of you have seen this recently? When I install in a local kind cluster I also get the same error.

ForwardedError: Plugin 'app' startup failed; caused by Error: Invalid app bundle schema. If this error is unexpected you need to run `yarn build` in the app. If that doesn't help you should make sure your config schema is correct and rebuild the app bundle again. Caused by the following schema error, Error: Config validation failed, Config must have required property 'techdocs' { missingProperty=techdocs } at 

Welcome your thoughts! If I can get this PR merged relatively quickly, there are some updates I want to make to the Postgres sub chart versions and contributing docs whilst I have time over the bank holiday here in the UK!

@ChrisJBurns tests are good now! Added just a small suggestion

[vinzscam]

FYI this won't be required anymore from the next version of Backstage as plugins will auto-configure service-to-service auth.
Of course let's keep it for now to get things unblocked

[sabre1041]

@vinzscam @tumido @sabre1041
Hi all, it seems that CI tests are failing now due to auth being enabled by default in the newer versions of Backstage. I've added a test secret just so we populate that value (even though in production users would add it via a secret)so the tests can continue. There is a weird couple of test scenarios whereby the auth.keys are only needed for two of the CI test values files we're using - which we may have to look into. Either way, it seems to have got past the auth.key issue now and onto a techdocs issue. Not sure if any of you have seen this recently? When I install in a local kind cluster I also get the same error.

ForwardedError: Plugin 'app' startup failed; caused by Error: Invalid app bundle schema. If this error is unexpected you need to run `yarn build` in the app. If that doesn't help you should make sure your config schema is correct and rebuild the app bundle again. Caused by the following schema error, Error: Config validation failed, Config must have required property 'techdocs' { missingProperty=techdocs } at 

Welcome your thoughts! If I can get this PR merged relatively quickly, there are some updates I want to make to the Postgres sub chart versions and contributing docs whilst I have time over the bank holiday here in the UK!

@ChrisJBurns tests are good now! Added just a small suggestion

As long as you define the techDocs section in your app-config.yaml file, you will not hit the parsing issue @ChrisJBurns ran into.

[vinzscam]

@vinzscam @tumido @sabre1041
Hi all, it seems that CI tests are failing now due to auth being enabled by default in the newer versions of Backstage. I've added a test secret just so we populate that value (even though in production users would add it via a secret)so the tests can continue. There is a weird couple of test scenarios whereby the auth.keys are only needed for two of the CI test values files we're using - which we may have to look into. Either way, it seems to have got past the auth.key issue now and onto a techdocs issue. Not sure if any of you have seen this recently? When I install in a local kind cluster I also get the same error.

ForwardedError: Plugin 'app' startup failed; caused by Error: Invalid app bundle schema. If this error is unexpected you need to run `yarn build` in the app. If that doesn't help you should make sure your config schema is correct and rebuild the app bundle again. Caused by the following schema error, Error: Config validation failed, Config must have required property 'techdocs' { missingProperty=techdocs } at 

Welcome your thoughts! If I can get this PR merged relatively quickly, there are some updates I want to make to the Postgres sub chart versions and contributing docs whilst I have time over the bank holiday here in the UK!

@ChrisJBurns tests are good now! Added just a small suggestion

As long as you define the techDocs section in your app-config.yaml file, you will not hit the parsing issue @ChrisJBurns ran into.

FYI the techdocs issue has been fixed, so from the next release the config won't be required either

[ChrisJBurns]

Cheers all! Apologies for late reply, have been away from keyboard!