You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of ExistingEntity(https://github.com/openconfig/gnsi/blob/main/certz/certz.proto#L580)message do we also send version and created on fields?.Here it's expected us to just copy the mentioned entity from existing profile. So is it implied that we copy version and created on fields as well for that particular entity from the profile mentioned in the request?
so my question is do we need to any version field checking for this type of rotate request? if yes then how?
Do we need to check versions between the destination profile entity(if present) and source profile entity? for example:
profile being rotated has a CertficateChain with version "v1.1".
As part of ExistingEntity(https://github.com/openconfig/gnsi/blob/main/certz/certz.proto#L580)message do we also send version and created on fields?.Here it's expected us to just copy the mentioned entity from existing profile. So is it implied that we copy version and created on fields as well for that particular entity from the profile mentioned in the request?
so my question is do we need to any version field checking for this type of rotate request? if yes then how?
Do we need to check versions between the destination profile entity(if present) and source profile entity? for example:
If thats the case then version and created on field should not be sent as part of ExistingEntity request.
https://github.com/openconfig/gnsi/blob/main/certz/certz.proto#L280
https://github.com/openconfig/gnsi/blob/main/certz/certz.proto#L542
The text was updated successfully, but these errors were encountered: