Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version handling in credentialz.proto #180

Open
dhilipkr opened this issue Apr 17, 2024 · 0 comments
Open

Version handling in credentialz.proto #180

dhilipkr opened this issue Apr 17, 2024 · 0 comments

Comments

@dhilipkr
Copy link

dhilipkr commented Apr 17, 2024

In gNSI, under authz, pathz, certz there seems to be an explicit mention to respond with a "ALREADY_EXISTS"/"AlreadyExists" when an RPC requests with the same version is being pushed again.
There seems to be a 'force_overwrite' flag that when set would ignore the above and allow the request even if the version is already in use.

There seems to be no such definition in credentialz.proto for the version string. Is this accidental or intentional? Is version and timestamp info only for telemetry data in credentialz? OR
Does credentialz also need to check the version in the incoming request and drop the request if the version already exists ? If so, is there a plan to add a 'force_overwrite' flag in credentialz.proto ?

Also, should version information from bootstrap configuration be persisted? or is it only required for Rotate RPC requests that come later after initial boot configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant