P1: @holodeck/provider-aws — aws.cloudwatch provider (metrics, alarms, history, discovery)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- aws, typescript
- Domain
- cloud, observability
Research direction
This is a whole provider lane, not a single change. Start with docs/ARCENTRY_PARITY.md and docs/PACKAGging.md in holodeck-sdk (sdk#23) to see the provider contract, and check whether runProviderConformance already exists in this repo. The issue also depends on a plan file outside the repo and on A2's partHint. Done means a aws.cloudwatch provider whose conformance suite passes against a fake client with no network calls. Scope it with a maintainer before picking it up.
Written by the indexing model from the issue text.
Description
Lane P1. aws.cloudwatch HolodeckProvider: GetMetricData batching with the poll period taken from the source; alarm states (DescribeAlarms); history; browse (namespace → metric → dimensions); discover via the Resource Groups Tagging API, with partHint from A2. Credentials come through provider secrets (access key / session token, or a Cognito identity pool), never in documents. permissions.network lists AWS origins. CI runs runProviderConformance against a fake client, with no network.
Plan: ~/dev/hyperdrive/.agents/plans/holodeck-arcentry-parity.md; parity matrix: docs/ARCENTRY_PARITY.md; contract: holodeck-sdk docs/PACKAGING.md (sdk#23).
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 10h 39m
- Merged PRs (30d)
- 38
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 hyperdrive-technology/holodeck
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hyperdrive-technology/holodeck#196 ·
Maintainers usually reply within 1 day
-
area:docs review-finding
Difficulty 1/5 Under an hour Newbie friendliness 70/100
hyperdrive-technology/holodeck#180 ·
Maintainers usually reply within 1 day
-
Flaky E3 test: native cut with no keydown (holodeck#123) in editing-ux-render.test.tsPossibly taken @dezlitz claimed this today. Openarea:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hyperdrive-technology/holodeck#141 ·
Maintainers usually reply within 1 day
-
assetUrlProblem: data:image check uses the un-normalised URL, so ' data:image/png...' is rejectedOpenarea:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hyperdrive-technology/holodeck#104 ·
Maintainers usually reply within 1 day
-
agent area:holodeck good first issue priority:p2
Difficulty 1/5 Under an hour Newbie friendliness 72/100
hyperdrive-technology/holodeck#64 ·
Maintainers usually reply within 1 day
All issues in hyperdrive-technology/holodeck
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenPetsHQ/openpets#273 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fritzprix/libr-agent#2161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
blackboardsh/electrobun#581 ·
-
backlog-skill effort:xs frontend infra ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
LucasSantana-Dev/Lucky#2862 ·
Maintainers usually reply within 1 day