Skip to content

fix(templates): don't hardcode an Anyscale-internal cloud in public template configs#925

Open
Aydin-ab wants to merge 1 commit into
mainfrom
fix/no-hardcoded-cloud
Open

fix(templates): don't hardcode an Anyscale-internal cloud in public template configs#925
Aydin-ab wants to merge 1 commit into
mainfrom
fix/no-hardcoded-cloud

Conversation

@Aydin-ab

@Aydin-ab Aydin-ab commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Public templates must not hardcode an Anyscale-internal cloud — a user in another org has no aws-public-us-west-2. creatives_diffusion_finetuning and fintech_fraud_risk both did, in their job compute config. Remove the cloud field entirely so it resolves to the org's default.

Testing

Config-only; the job compute config isn't exercised by /test-template (workspace path). Correctness by inspection.

https://claude.ai/code/session_01QmLc4yWtmC3PX2NwWzPbzD

…template configs

creatives_diffusion_finetuning and fintech_fraud_risk hardcoded `cloud: aws-public-us-west-2`
(an Anyscale-internal cloud) in their job compute config — a user running these public templates
in another org has no such cloud, so the job fails to launch. Drop the `cloud` field entirely so
it resolves to the org's default.

Claude-Session: https://claude.ai/code/session_01QmLc4yWtmC3PX2NwWzPbzD
Signed-off-by: Aydin Abiar <aydin@anyscale.com>
@Aydin-ab
Aydin-ab force-pushed the fix/no-hardcoded-cloud branch from 610242f to ac7f410 Compare July 22, 2026 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant