It appears Director calls CredHub for a single secret twice during a deployment. Here are the Director calls:
1) Calls CredHub with a GET by name. In this case the query name parameter value is the identifier from the deployment manifest file.
2) Calls CredHub with a GET by ID using the id value for the secret returned in the first call.

Can someone explain why Director appears to be making two calls for the same secret during a deployment?

Thanks.

Mike

we havent spent any time optimizing it since it shuold be pretty cheap to
make these calls. are you concerned about the perf aspect of it or
something else?

On Fri, Sep 22, 2017 at 10:55 AM, Michael Stancampiano <mstancamp(a)gmail.com>
wrote:

It appears Director calls CredHub for a single secret twice during a
deployment. Here are the Director calls:
1) Calls CredHub with a GET by name. In this case the query name parameter
value is the identifier from the deployment manifest file.
2) Calls CredHub with a GET by ID using the id value for the secret
returned in the first call.

Can someone explain why Director appears to be making two calls for the
same secret during a deployment?

Thanks.

Mike

Performance is an issue, but just understanding the logic on why Director would make two calls during a deployment to obtain the same secret is important.

Thanks.