feat: add multiple env support #232

RoxyFarhad · 2025-12-18T12:03:03Z

This PR introduces a new naming convention to support multiple environment deployments:

Environment Label (environment-label): The pre-defined deployment target you specify when triggering the workflow (dev, staging, prod-multitenant). This is what you select from the dropdown in GitHub Actions.
Environment Name (env-name): The actual environment names defined in your environments.yaml file (dev.aws, dev.azure, staging, etc.). These are the specific deployment configurations that map to the environment label.

Why we need this distinction:

One-to-Many Mapping: A single environment label can now map to multiple environment names (e.g., dev → dev.aws, dev.azure), enabling parallel deployments to different cloud providers
Non-explicit Mapping: If an environment has an env-name that is the same as the deployment target (i.e. an env-name of dev and a deployment target dev) it will automatically deploy to that environment.

This supports the desired config change of having different environments that map to a single "environment":

schema_version: "v1" # This is used to validate the file structure and is not used by the agentex CLI
environments:
  dev-aws:
    environment: "dev"
    kubernetes:
      namespace: "sgp-000-hello-acp"
    auth:
      principal:
        user_id: ...
        account_id: ...
    helm_overrides:
      ...
  dev-azure:
    environment: "dev"
    kubernetes:
      namespace: "sgp-000-hello-acp"
    auth:
      principal:
        user_id: ...
        account_id: ...
    helm_overrides:
      ...

Backwards compatability:

This introduces new helper methods that are used in the deployment pipelines and doesn't change any existing methods. This is purely an additive change so it will not break any older code, or anyone using these helper function sin older SDKs.

Tests against internal scale agents:

New Process (NB. all agents that did not deploy was not because of this new code)
Old Process - N.B. the deployment failed because the agent doesn't have the correct creds setup but the deployment to the cluster works correctly.

N.B. There was a large diff generated by linter for some reason

socket-security · 2025-12-18T12:03:34Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	agentex-sdk@0.6.7 ⏵ 0.8.0	⁺¹⁴

View full report

src/agentex/lib/sdk/config/environment_config.py

RoxyFarhad · 2025-12-18T12:09:02Z

src/agentex/lib/sdk/config/environment_config.py

-        description="Helm repository name for the environment"
+
+    kubernetes: AgentKubernetesConfig | None = Field(default=None, description="Kubernetes deployment configuration")
+    environment: str | None = Field(


this is the only change in the file

RoxyFarhad · 2025-12-18T12:09:15Z

src/agentex/lib/sdk/config/environment_config.py

        return self.environments[env_name]
-
+
+    def get_configs_for_env(self, env: str) -> List[AgentEnvironmentConfig]:


new method added

RoxyFarhad · 2025-12-18T12:09:52Z

tests/lib/cli/test_environment_config.py

+)
+
+
+class TestAgentEnvironmentsConfig:


added a tests file for this new functionality

RoxyFarhad · 2025-12-18T12:17:42Z

src/agentex/types/__init__.py

-from .deployment_history_list_response import DeploymentHistoryListResponse as DeploymentHistoryListResponse
 from .task_retrieve_by_name_params import TaskRetrieveByNameParams as TaskRetrieveByNameParams
 from .message_list_paginated_params import MessageListPaginatedParams as MessageListPaginatedParams
+from .deployment_history_list_params import DeploymentHistoryListParams as DeploymentHistoryListParams


fixing linter error

RoxyFarhad · 2025-12-18T16:23:17Z

src/agentex/_client.py


        return TrackerResource(self)

+    @cached_property


This was a valid linter error that was being ignored but that we should support in the SDK

RoxyFarhad · 2025-12-22T11:35:19Z

src/agentex/lib/sdk/config/environment_config.py

        return self.environments[env_name]
-
+
+    def get_configs_for_env(self, env_target: str) -> dict[str, AgentEnvironmentConfig]:


New Addition

RoxyFarhad · 2025-12-22T11:36:49Z

src/agentex/lib/sdk/config/validation.py

            )
-
+
+    # if environment mappings are set, you cannot have a top-level env_name that maps to an `environment: value`


not sure if this is worth removing?

I think this is a reasonable sanity check to keep especially as we migrate to this new format

RoxyFarhad · 2025-12-22T11:37:29Z

src/agentex/lib/sdk/config/validation.py

        missing_envs: List[str] = []
+        environment_mappings = [env.environment for env in environments_config.environments.values() if env.environment]
+        top_level_envs = [env for env in environments_config.environments]
+        all_envs = set(environment_mappings + top_level_envs)


this shouldn't be a breaking change because we are still adding the same [env for env in environments_config.environments] in the check but we have just moved it above.

RoxyFarhad · 2025-12-22T11:56:02Z

.github/workflows/main.yml

@@ -1,6 +0,0 @@
-name: Test AgentEx Tutorials


This was a drive-by removal: Removing this because its not used and just errors on every workflow

RoxyFarhad commented Dec 18, 2025

View reviewed changes

src/agentex/lib/sdk/config/environment_config.py Outdated Show resolved Hide resolved

RoxyFarhad commented Dec 18, 2025

View reviewed changes

adding the multiple env mapping feature

f2e47c5

RoxyFarhad force-pushed the RF/support-multiple-envs branch from 5927953 to f2e47c5 Compare December 18, 2025 12:10

RoxyFarhad commented Dec 18, 2025

View reviewed changes

fixing errors

5259f20

RoxyFarhad force-pushed the RF/support-multiple-envs branch from e2aa69e to 5259f20 Compare December 18, 2025 12:29

RoxyFarhad added 4 commits December 18, 2025 14:48

fixing this

c15a86c

new one

6c7bf65

small fix

be68303

fixing validation

7881ec2

RoxyFarhad commented Dec 18, 2025

View reviewed changes

RoxyFarhad force-pushed the RF/support-multiple-envs branch from 2f8c94b to 7881ec2 Compare December 18, 2025 17:39

RoxyFarhad added 2 commits December 18, 2025 18:21

update the tests

42a0727

fixing the linter

0c3a8c2

RoxyFarhad force-pushed the RF/support-multiple-envs branch from c55c9e4 to 0c3a8c2 Compare December 19, 2025 12:43

RoxyFarhad commented Dec 22, 2025

View reviewed changes

RoxyFarhad added 2 commits December 22, 2025 11:52

Merge branch 'main' into RF/support-multiple-envs

f7809d6

removing the main yaml

b8af1f0

RoxyFarhad commented Dec 22, 2025

View reviewed changes

RoxyFarhad requested a review from a team December 22, 2025 12:26

smoreinis approved these changes Dec 23, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add multiple env support #232

feat: add multiple env support #232

RoxyFarhad commented Dec 18, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Dec 18, 2025 •

edited

Loading

Uh oh!

Uh oh!

RoxyFarhad Dec 18, 2025

Uh oh!

RoxyFarhad Dec 18, 2025

Uh oh!

RoxyFarhad Dec 18, 2025

Uh oh!

RoxyFarhad Dec 18, 2025

Uh oh!

RoxyFarhad Dec 18, 2025

Uh oh!

RoxyFarhad Dec 22, 2025

Uh oh!

RoxyFarhad Dec 22, 2025

Uh oh!

smoreinis Dec 23, 2025

Uh oh!

RoxyFarhad Dec 22, 2025

Uh oh!

RoxyFarhad Dec 22, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		return self.environments[env_name]


		def get_configs_for_env(self, env: str) -> List[AgentEnvironmentConfig]:

		return self.environments[env_name]


		def get_configs_for_env(self, env_target: str) -> dict[str, AgentEnvironmentConfig]:

		)


		# if environment mappings are set, you cannot have a top-level env_name that maps to an `environment: value`

		)


		class TestAgentEnvironmentsConfig:

feat: add multiple env support #232

Are you sure you want to change the base?

feat: add multiple env support #232

Conversation

RoxyFarhad commented Dec 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Dec 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

RoxyFarhad Dec 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

RoxyFarhad commented Dec 18, 2025 •

edited

Loading

socket-security bot commented Dec 18, 2025 •

edited

Loading

RoxyFarhad Dec 22, 2025 •

edited

Loading