Skip to content

Conversation

@IvanKolchanov
Copy link
Contributor

@IvanKolchanov IvanKolchanov commented Jun 26, 2024

Resolves #341

@IvanKolchanov IvanKolchanov marked this pull request as ready for review June 27, 2024 19:01
Task<QueryResult<LocalServiceHealth>> GetLocalServiceHealthByID(string serviceID, QueryOptions q, CancellationToken ct = default);
Task<QueryResult<LocalServiceHealth>> GetLocalServiceHealthByID(string serviceID, CancellationToken ct = default);
Task<QueryResult<Metrics>> GetAgentMetrics(CancellationToken ct = default);
Task<WriteResult<AgentAuthorizeResponse>> ConnectAuthorize(AgentAuthorizeParams parameters, CancellationToken ct = default);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can also add an overload with query options.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yeah, that makes a lot of sense. Haven't seen that pattern in code with WriteResult so it didn't occur to me. Will implement.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I didn't notice this is a write request, in this case we use WriteOptions instead of QueryOptions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep yep, that's what I thought. Just pushed the commit, waiting for the tests to run!

…overload to ConnectAuthorize to support WriteOptions
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.

[FEATURE REQUEST]: Connect Authorize, tests whether a connection attempt is authorized between two services

2 participants