Expose Provisioning States via Cache interface #48115
Conversation
tcsc
added
the
no-changelog
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
| // DownstreamProvisioningStates defines an interface for managing principal | ||
| // provisioning state records scoped by a target downstream receiver. | ||
| type DownstreamProvisioningStates interface { | ||
| type DownstreamProvisioningStateGetter interface { |
There was a problem hiding this comment.
Is this going to be used later?
There was a problem hiding this comment.
Yes, This interface will be use in e https://github.com/gravitational/teleport.e/pull/5191
| } | ||
| defer rg.Release() | ||
|
|
||
| return rg.reader.GetProvisioningState(ctx, downstream, id) |
There was a problem hiding this comment.
Is this going to benefit from having a read through on NotFound? We have that for some point get operations.
There was a problem hiding this comment.
This can be added later. Currently, there doesn’t seem to be a case where GetProvisioningState needs to reach the backend when NotFound. The AWS IC provisioning logic is self-healing, so if the provisioning state hasn’t yet successfully propagated to the cache, the provisioning operation will be retried.
public-teleport-github-review-bot
bot
removed the request for review
from bernardjkim
No description provided.