dax: standardize declaw resources via node-large template#197
Merged
HeyGarrison merged 1 commit intoJul 18, 2026
Conversation
Contributor License AgreementAll contributors are covered by a CLA. |
Author
|
Hi @HeyGarrison — this is a one-line follow-on to #196: it adds I based it on your Thanks! |
Adds declaw to DAX_RESOURCE_OPTIONS so it targets the same 8 vCPU / 16 GiB profile as the other providers in the map. The node-large template provisions 8 vCPU / 16 GiB RAM with an 8 GiB disk overlay. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
shivam-declaw
force-pushed
the
declaw-node-large-for-dax
branch
from
July 18, 2026 02:14
e89c89b to
d2e6f83
Compare
HeyGarrison
merged commit Jul 18, 2026
f0efe46
into
computesdk:fix/dax-standardize-resources
3 checks passed
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.
Builds on #196 — adds
declawtoDAX_RESOURCE_OPTIONSso it targets the same 8 vCPU / 16 GiB profile the other providers are standardized to.declaw selects resource sizing by template rather than by per-field cpu/memory options, so the standardized profile is expressed as a template id.
node-largeprovisions 8 vCPU / 16 GiB RAM with an 8 GiB disk overlay. The@computesdk/declawadapter forwardstemplateIdstraight through to sandbox creation, so the single map entry is all that's needed:This is targeted at the
fix/dax-standardize-resourcesbranch so it folds into #196 as one change rather than a competing one. Happy to retarget tomainif you'd rather land them separately.