Skip to content

Snowflake Apps: always use managed compute pools - #3129

Merged
sfc-gh-gbloom merged 1 commit into
mainfrom
gbloom/snowflake-apps-managed-compute-pools
Jun 22, 2026
Merged

sfc-gh-gbloom merged 1 commit into
mainfrom
gbloom/snowflake-apps-managed-compute-pools

Conversation

@sfc-gh-gbloom

@sfc-gh-gbloom sfc-gh-gbloom commented Jun 22, 2026 •

Copy link
Copy Markdown
Contributor

Pre-review checklist

  • If my changes add or modify user-facing interface (commands, flags, output formats), I consulted maintainers and got sign-off beforehand (how).
  • I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
  • I've added or updated unit tests to verify correctness of my new code.
  • I've added or updated integration tests to verify correctness of my new code.
  • Manually tested on macOS
  • Manually tested on Windows
  • I've confirmed my changes are up-to-date with the target branch.
  • I've described my changes in RELEASE-NOTES.md (see when and how).
  • I've updated documentation if behavior changed.

Changes description

Snowflake App Runtime services now always run on server-managed compute pools, so the CLI no longer configures compute pools.

  • snow app setup no longer writes build_compute_pool / service_compute_pool to the generated snowflake.yml, and no longer prints them in the resolved-config / --dry-run / JSON output. The hidden --compute-pool flag is now a no-op, kept only for backward compatibility.
  • The DEFAULT_SNOWFLAKE_APPS_BUILD_COMPUTE_POOL / DEFAULT_SNOWFLAKE_APPS_SERVICE_COMPUTE_POOL account parameters are no longer fetched or resolved.
  • Existing projects that set build_compute_pool / service_compute_pool in snowflake.yml keep working: the fields stay parseable and snow app deploy still forwards them to the server.

@sfc-gh-gbloom
sfc-gh-gbloom marked this pull request as ready for review June 22, 2026 15:22
@sfc-gh-gbloom
sfc-gh-gbloom requested review from a team as code owners June 22, 2026 15:22
@sfc-gh-gbloom sfc-gh-gbloom changed the title Snowflake Apps: always use server-managed compute pools Snowflake Apps: always use managed compute pools Jun 22, 2026
`snow app setup` no longer writes `build_compute_pool` /
`service_compute_pool` to the generated `snowflake.yml`, and the
`DEFAULT_SNOWFLAKE_APPS_BUILD_COMPUTE_POOL` /
`DEFAULT_SNOWFLAKE_APPS_SERVICE_COMPUTE_POOL` account parameters are no
longer fetched. App services always run on server-managed compute pools.

Existing projects that set these fields in `snowflake.yml` continue to be
honored by `snow app deploy` (the fields remain parseable and are still
forwarded to the server).

Co-authored-by: Cursor <cursoragent@cursor.com>
@sfc-gh-gbloom
sfc-gh-gbloom force-pushed the gbloom/snowflake-apps-managed-compute-pools branch from de88ed4 to 5f7a336 Compare June 22, 2026 17:08
@sfc-gh-gbloom
sfc-gh-gbloom enabled auto-merge (squash) June 22, 2026 18:02
@sfc-gh-gbloom
sfc-gh-gbloom merged commit 818f8d9 into main Jun 22, 2026
30 checks passed
@sfc-gh-gbloom
sfc-gh-gbloom deleted the gbloom/snowflake-apps-managed-compute-pools branch June 22, 2026 21:29
snowflake-copybara Bot pushed a commit that referenced this pull request Jul 17, 2026
Snowflake Apps: always use server-managed compute pools

`snow app setup` no longer writes `build_compute_pool` /
`service_compute_pool` to the generated `snowflake.yml`, and the
`DEFAULT_SNOWFLAKE_APPS_BUILD_COMPUTE_POOL` /
`DEFAULT_SNOWFLAKE_APPS_SERVICE_COMPUTE_POOL` account parameters are no
longer fetched. App services always run on server-managed compute pools.

Existing projects that set these fields in `snowflake.yml` continue to be
honored by `snow app deploy` (the fields remain parseable and are still
forwarded to the server).

Co-authored-by: Cursor <cursoragent@cursor.com>
GitOrigin-RevId: 818f8d9
snowflake-copybara Bot pushed a commit that referenced this pull request Jul 29, 2026
Snowflake Apps: always use server-managed compute pools

`snow app setup` no longer writes `build_compute_pool` /
`service_compute_pool` to the generated `snowflake.yml`, and the
`DEFAULT_SNOWFLAKE_APPS_BUILD_COMPUTE_POOL` /
`DEFAULT_SNOWFLAKE_APPS_SERVICE_COMPUTE_POOL` account parameters are no
longer fetched. App services always run on server-managed compute pools.

Existing projects that set these fields in `snowflake.yml` continue to be
honored by `snow app deploy` (the fields remain parseable and are still
forwarded to the server).

Co-authored-by: Cursor <cursoragent@cursor.com>
GitOrigin-RevId: 818f8d9
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.

2 participants