Repository navigation
cost: three months priced, from the module's defaults and the lists the AWS pricing page loads - #69
Merged
Merged
Conversation
…he AWS pricing page loads The cost page named the parts and sent the reader to the calculator with no figure to start from. tools/pricing reads what the module starts by default at the pinned commit - the control plane's and the proxy's machine, the runners' types, the most runners - and prices them on demand in each region Spin OS has images in, from the per-region lists the AWS pricing page itself loads, dated by AWS's publication and by the day written. The page draws three months from it: nothing running, one runner on working hours, the most runners around the clock. The daily sync rewrites the record and reference:check refuses one a month old or of other machines than the module's, so a figure on the page is never quietly stale. Spot, storage and transfer stay the calculator's: no public list prices a spot hour, and the other two depend on use. Co-Authored-By: Claude Fable 5.1 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Phase 4 of the plan that answers the October review: dated, generated cost scenarios.
tools/pricing: readsinstance_type,proxy_instance_type(modules/controlplane),instance_typesandmax_hosts(modules/runners) from the spin-terraform-aws checkout at its pin, and each type's on-demand Linux price inus-east-1andus-west-2from the per-region JSON the AWS pricing page loads (about 650 KB a region; the bulk price list is 475 MB).src/data/pricing.jsoncarries the day written, AWS's publication date, the machines and the prices.-checkfails on a record older than 30 days or of other machines than the module's defaults: inreference:checkandreference:public.sources:bump(the daily sync) rewrites it.aws/cost.mdx: "Three months, priced" - nothing running; one runner on working hours (176 h); the most runners (max_runners' default) around the clock - a column a region, on demand, with the two dates. Spot, storage and transfer stay the calculator's, said why.go test ./tools/...,task checkgreen (378 pages, every link resolves).Plan: https://claude.ai/artifact/3cdj5BJsAkTtS9pWVhwksW (fase 4).
🤖 Generated with Claude Code