Allow to Select Agent in Environment Folder setting page
Problem to solve
With Allow to Select Agent in Environment setting page (#396407 - closed), users can set an agent to an environment, but if environments are created dynamically (e.g. Review Apps) setting one by one for each environment is cumbersome task so there should be a way to set an agent to multiple environments at once.
One workaround would be to set it via Environment API or GraphQL in pipeline job script.
FYI, we used to use environment scope pattern for such usecase, but We do not go for it this time. See this comment.
Proposal
Similar to Allow to Select Agent in Environment setting page (#396407 - closed), users want to select agent for a specific environment folder.
- User visits Project > Deployments > Environments. This is Environment index page.
- User expands an environment folder and clicks "Show All" button, which navigates to Environment Folder index page
- User clicks "Edit" button. (This doesn't exist yet, we will add this)
- User selects an available agent from dropdown list.
The order of precedence for agents is (from highest to lowest):
- Environment's agent.
- Environment folder's agent.
Technical details
- We don't have data model for environment folders. We likely need to introduce a new table e.g.
environment_folders
.
# New table
environment_folders:
name:
agent_id:
# Existing table
environments:
name:
agent_id: FK to cluster_agents table.
folder_id: FK to environment_folders table.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.