KV Store config not read in tyk.conf (security.certificates.upstream) about tyk HOT 4 CLOSED

Hi @matthewdickinson,
I'm sorry for the slow reply - and (echoing my comments there) thank you for raising this on the Community forum.

To confirm my response there, you can currently access the following fields in tyk.conf from a KV store:

secret
node_secret
storage.password
cache_storage.password
security.private_certificate_encoding_secret
db_app_conf_options.connection_string
policies.policy_connection_string

Extending this list is sadly not in scope for the upcoming 5.3.0 release, however we do want to improve coverage but I can't give you a time frame at the moment for when this can be done.

from tyk.

Hi @matthewdickinson,

At present the only fields from the API definition that can be stored in KV are:

• listen path
• target URL

This is mentioned here in the documentation - I agree this is not very clear.

You'll be pleased to hear that we're actually planning to extend this capability to cover a lot more of the API definition in the upcoming Tyk 5.3.0 release. From that release you'll be able to store any string field from your API definition in your centralised secret store.

from tyk.

Hi @matthewdickinson,

At present the only fields from the API definition that can be stored in KV are:

• listen path
• target URL

This is mentioned here in the documentation - I agree this is not very clear.

You'll be pleased to hear that we're actually planning to extend this capability to cover a lot more of the API definition in the upcoming Tyk 5.3.0 release. From that release you'll be able to store any string field from your API definition in your centralised secret store.

I am pleased to hear that! However, the documentation says (without caveat) that it can be used in tyk.conf, and that's where I'm trying to use the security.certificates.upstream, but it doesn't work. Will that be getting support?

from tyk.

@andyo-tyk Will that release add any further field coverage in tyk.conf?

from tyk.