[feature] Universal remote-like variables exposed to tomes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
Research direction
No files or tests are named. The work is a design for Eldritch tomes to resolve large remote variables over the existing agent callback/transport instead of embedding secrets. Start by finding how tomes are executed and how the agent talks to the server (transport types, assets/cdn). Agree on remote-reference vs cache/TTL before coding; done is runtime lookup of keyed server-side values without writing secrets to disk.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Recently, I've been toying with imix beacons on k8s nodes. I run into scenarios where I try to use SA tokens extracted from the node level access, or secrets from env vars, where I want use those secrets in other tomes to pivot/etc.
It would be nice if the Eldritch language supports the idea of remote variables especially large base64 encoded strings. this could be nice for things other things like LDAP dumps, cloud IAM temporary credentials especially those extracted through imds, windows stuff (ew), etc. Using AI with tomes it often tries to copy/paste large strings and either fails especially or eats up $ costly output in tokens.
Describe the solution you'd like
This might take some tinkering with the transport types but with each callback it would be nice if the agent could pick up these remote variables or have a mechanism to know where they are keyed on the server when an eldritch function/variable references them. Not quite if this should be a buffer-like approach or something similar to LRU caching, or just remote reference that gets resolved at runtime with stored metadata in memory.
Describe alternatives you've considered
Alternatives would be writing secrets to files and then using them, but obliviously, that is a bad idea. Using external K/V stores is annoying and to lose the niceties of realm crypto over wide transport type when querying out. Same with random https webhooks to retrieve secrets.
I see there is an "assets/cdn" ability but this feels more-like object style storage of things used during an engagement rather than TTL based secrets.
- Dominant language
- Rust
- Stars
- 639
- Forks
- 65
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 62
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spellshift/realm
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spellshift/realm#2509 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
spellshift/realm#1574 · 3 comments ·
Maintainers usually reply within 1 day
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 55/100
spellshift/realm#2461 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 5/5 Over a week Newbie friendliness 15/100
spellshift/realm#2449 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
spellshift/realm#2424 ·
Maintainers usually reply within 1 day
All issues in spellshift/realm
Similar issues
-
<input type="number"> misses text-entry leaf sizing in layoutPossibly taken @GoCoder7 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
DioxusLabs/blitz#1675 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
metasequoiaime/msime#11666 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
bug drawings help wanted ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
userFRM/egui-charts#3479 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
s2-streamstore/cachey#225 ·
Maintainers usually reply within 1 day