proposal: per-lease provider options
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- api
Research direction
This is a design proposal, not a task. Start by reading the hard-coded provider fields in packages/contracts/src/remote-config-fields.ts (around line 28) and how they reach the core client contract. The proposed leases.allocate({ leaseProvider, providerOptions }) API and plugin validation are still undecided. Done would be an agreed design, not a patch; coordinate with the maintainers first.
Written by the indexing model from the issue text.
Description
Part of #3747. Proposal; not scheduled.
Problem
- Provider options are hard-coded into core. Provider-specific request options are fixed fields of the core client contract (
packages/contracts/src/remote-config-fields.ts:28:awsProjectArn,providerApp, …). - Nothing provider-specific reaches a single lease. Instance identity and credentials therefore belong to the whole daemon. That's why e2e runs one daemon per worker.
Proposal
- The API.
leases.allocate({ leaseProvider, providerOptions }), validated by the plugin. It would replace the hard-coded fields. - What it would allow:
- one daemon serving many workers;
@agent-device/limrunowning instance creation: model, OS version, timeout and labels.
Status
This needs a design pass before it's scheduled. It must not block #3755 or #3757.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 334
- Avg merge
- 12h 2m
- Merged PRs (30d)
- 678
Getting set up
- No Dockerfile or Docker Compose file
- No 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 callstack/agent-device
-
`devices` reports a phantom Android emulator named after the emulator's crashdata INFO bannerPossibly taken @airowe claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
callstack/agent-device#3716 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
Maintainers usually reply within 1 day
-
backlog refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
callstack/agent-device#3759 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 15/100
callstack/agent-device#3757 ·
Maintainers usually reply within 1 day
-
feat(provider-testmu): publish @agent-device/testmu on plugin contract v2Possibly taken A pull request linked to this issue is open or already merged. Openenhancement ready-for-agent
Difficulty 4/5 3-5 days Newbie friendliness 35/100
callstack/agent-device#3756 ·
Maintainers usually reply within 1 day
All issues in callstack/agent-device
Similar issues
-
bug engine
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
frostney/GocciaScript#1746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
agilepathway/label-checker#739 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
CopilotKit/OpenBot#800 ·
Maintainers usually reply within 1 day
-
Endpoint links in the tag operations list are below the 24px target sizePossibly taken @AdzerKI claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
ehmpathy/rhachet-roles-bhuild#471 ·
Maintainers usually reply within 1 day