Ensure Active Spring Profile with BIP config fix

[nelsestu]

What was the problem?

With Spring Profiles now active in Dev, I stumbled onto the fact that the claimBaseUrl property we consume as a config setting is in fact a hostname. Interpretting the config name claimBaseUrl, I mistakenly set the config value to a URL such as https://claims-dev... This results in a duplicate protocol prefix.

Associated tickets or Slack threads:

• Resolve BIP Connection Issues in LHDI Dev #2298, Pair to complete BIP Rollout to Remaining LHDI Envs (except prod) #2297
• precursor PR - Add config for the dev environment via application-dev.yaml #2328

How does this fix it?¹

This pull request modifies how we consume the claimBaseUrl setting, so that we can safely allow for either specification.

Footnotes

1. Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. ↩

[github-actions]

Test Results

144 tests  ±0   144 ✔️ ±0   46s ⏱️ ±0s
  39 suites ±0       0 💤 ±0 
  39 files   ±0       0 ❌ ±0 

Results for commit 069714f. ± Comparison against base commit 5e02efb.

[github-actions]

JaCoCo Test Coverage

There is no coverage information present for the Files changed

Total Project Coverage	76.17%	❌

[dfitchett]

Do you also need app/docker-compose.yml to be updated for the svc-bip-api to include the ENV var? It would need *common-vars to be added to the environment.

...
  svc-bip-api:
    profiles: ["all", "svc", "bip"]
    image: va/abd_vro-svc-bip-api:latest
    environment:
      <<: [ *rabbitmq-placeholder-vars , *common-vars]
...