Remote Dev Plugin Part 1 - Register the remote dev plugin and add utils

[sfc-gh-zzhu]

Pre-review checklist

• I've confirmed that instructions included in README.md are still correct after my changes in the codebase.
• I've added or updated automated unit tests to verify correctness of my new code.
• I've added or updated integration tests to verify correctness of my new code.
• I've confirmed that my changes are working by executing CLI's commands manually on MacOS.
• I've confirmed that my changes are working by executing CLI's commands manually on Windows.
• I've confirmed that my changes are up-to-date with the target branch.
• I've described my changes in the release notes.
• I've described my changes in the section below.

Changes description

This PR adds a new remote plugin to the Snowflake CLI that provides functionality for creating and managing remote development environments. The implementation includes:

1. Core constants and configuration for remote development environments
2. Utilities for working with Snowflake regions and compute resources
3. Container specification generation for SPCS-based remote environments

The plugin aims to enable users to create remote development environments with appropriate resource configurations based on the selected compute pool, including support for both CPU and GPU instances across different cloud providers. More details can be found in https://docs.google.com/document/d/1M0gV7soTy3dOadwgaUQrdKdkgR6YEUiwmBgMPlj_h5I/edit?usp=sharing

[sfc-gh-zzhu]

• Add default block volume for persistent storage #2660
• Address feedbacks #2636
• Remote Dev Plugin Part 4 - bug fix and feature improvement #2569
• Remote Dev Plugin Part 3 - Enable remote ssh connection #2547
• Remote Dev Plugin Part 2 - Add basic remote commands #2546
• Remote Dev Plugin Part 1 - Register the remote dev plugin and add utils #2545 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Logic error: The fallback logic will cause a KeyError when the instance_family is not found in COMMON_INSTANCE_FAMILIES. The code uses or operator which means if COMMON_INSTANCE_FAMILIES.get(instance_family) returns None, it will try to access CLOUD_INSTANCE_FAMILIES[cloud][instance_family] without checking if the key exists. This should use proper error handling or check if the key exists in the cloud-specific families before accessing it.

Suggested change

	return (
	COMMON_INSTANCE_FAMILIES.get(instance_family)
	or CLOUD_INSTANCE_FAMILIES[cloud][instance_family]
	)
	return (
	COMMON_INSTANCE_FAMILIES.get(instance_family)
	or CLOUD_INSTANCE_FAMILIES.get(cloud, {}).get(instance_family)
	)

Spotted by Diamond



Is this helpful? React 👍 or 👎 to let us know.