feat: add fetch_api_boundary_nodes API to ic-agent #509
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
API boundary nodes were recently added to the certified state tree. Currently, there are no API boundary nodes and the subtree is empty. accordingly. API boundary nodes will be added to the registry via NNS proposals at some later stage.
IC clients should be able to retrieve all these API BNs in a convenient way.
This PR extends
ic-agent
API with a new method:pub async fn fetch_api_boundary_nodes() -> Vec<ApiBoundaryNode>
How Has This Been Tested?
system-test
. This test converts two unassigned nodes into API BNs.agent
with any IC replica url provided insystem-test
logs during test execution.let api_bns = agent.fetch_api_boundary_nodes(effective_canister_id).await
.State Tree
.Checklist: