It would be nice to have a way to supply a single CA certificate that will be inherited by all of the terafoundation connectors automatically. We began implementing this idea in #3584, but it was not as straight forward as anticipated.
Our options:
run a transform on the sysconfig before validation. This might cause errors with defaults that are applied during validation.
validate the sysconfig, run a transform, then validate again.
add the global cert to each connector when we create the client. This would have to be added to createClient within terafoundation/src/api/index.ts, but also anywhere else a client is created using some other method.
It would be nice to have a way to supply a single CA certificate that will be inherited by all of the terafoundation connectors automatically. We began implementing this idea in #3584, but it was not as straight forward as anticipated.
Our options:
createClient
withinterafoundation/src/api/index.ts
, but also anywhere else a client is created using some other method.ref: #1070