SPS shared services account (i.e. Data Catalog) communication/routing

[galenatjpl]

For 23.2, the project account will be split out from the shared services account, and SPS will need to communicate to services in the shared account.
For example, communicating from the Unity-Sips-Test account to the DAPA API on the Unity-Test account.

Acceptance Criteria

• the communication is proven to work, cross accounts

[LucaCinquini]

I hope this will be seamless to us - i.e. simply using the proper value of the DAPA URL.

[galenatjpl]

@LucaCinquini Yes, hopefully this can be setup in a seamless way. Currently, is the DAPA URL hardcoded in your software, or is it in a config file, or is it in terraform config? I think that the long-term best way is that this gets specified as a deployment param, and gets injected into terraform (or some other appropriate place) during deployment, but the actual value is not actually in any of your repositories.

[LucaCinquini]

Yes that is currently the case - it's a parameter specified in the terraform.tfvars file