Skip to content

Require client identity for registering operations#615

Merged
abernix merged 2 commits intoabernix/register-operationsfrom
jbaxleyii/register-operations-client-identity
Oct 4, 2018
Merged

Require client identity for registering operations#615
abernix merged 2 commits intoabernix/register-operationsfrom
jbaxleyii/register-operations-client-identity

Conversation

@jbaxleyiii
Copy link
Copy Markdown
Contributor

@abernix this adds client identity to the registration step!

James Baxley added 2 commits October 4, 2018 11:24
Operations needs to be attached to a specific client
so this PR adds the ability to send a client name,
client id, and client version to annoate the manifest
of operations. This will make it much easier to validate
schema changes against registered queries and have
a sane governace strategy
A point of clarity, client identifier is a better term for a value
that can range from UUID, abritray strings, certs, and really
anything else. Client Id was leading to confusion about the generation
state and possible values (i.e. id's are typically a monotype)
@abernix abernix merged commit e78ab45 into abernix/register-operations Oct 4, 2018
@abernix abernix deleted the jbaxleyii/register-operations-client-identity branch October 4, 2018 16:16
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

Successfully merging this pull request may close these issues.

2 participants