Metadata and Ordering Features for Conduits
I’d like to suggest adding some features to improve conduit management:
- Conduit Ordering and Metadata:
- Introduce an ordering system for conduits (e.g., 0, 1, 2, 3, 4) to help with organization and tracking.
- Add metadata fields such as creation time and a custom name or identifier to each conduit. This will make it easier to manage and differentiate between conduits.
Example Data:
{
"data":[
{
"id":"26b1c993-bfcf-44d9-b876-379dacafe75a",
"shard_count":15,
"index":"0"
},
{
"id":"bfcfc993-26b1-b876-44d9-afe75a379dac",
"shard_count":5,
"index":"2"
}
]
}
Proposed structure (requires v2):
{
"data":[
{
"0":{
"id":"26b1c993-bfcf-44d9-b876-379dacafe75a",
"shard_count":15
},
"1":{
},
"2":{
"id":"bfcfc993-26b1-b876-44d9-afe75a379dac",
"shard_count":10
},
"3":{
"id":"cab6c993-bfcf-tfd9-0876-3g9d6c8fe15t",
"shard_count":5
},
"4":{
}
}
]
}
Use Case:
- I’m working on managing multiple bots with different conduits, such as:
- Bot X with conduit 0 and up to 10 shards.
- Bot Y with conduit 1.
- Bot Z with conduit 2, etc.
I need to be able to:
- Scale conduit 0 by checking its shards, updating or deleting as necessary.
Reasoning:
These changes would help in managing conduits more effectively and prevent issues when users delete or recreate conduits. It would also make it easier to scale and organize bots efficiently.
2
votes