Function Compute:Manage environments

Before you begin

• By default, no domain name is assigned to an environment. To use different domain names for different environments, specify the customDomains field in the s.yaml file of your repository.

• Hosting Alibaba Cloud resources (SLS, VPC, NAS) in an environment requires the corresponding service permissions. Attach the required policies to the AliyunFCServerlessDevsRole role.

• A service can be deployed in multiple environments. You can determine whether to use the configurations provided by the environment.

Create an environment

1. Log on to the Function Compute console and open the application details page.

2. Click Create Environment.

3. Configure the following parameters:

   Parameter	Description
   Environment Name	A descriptive name to distinguish this environment. An environment type can have multiple named environments.
   Environment Type	The category for filtering: test, staging, or production.
   Description	Basic information such as region and role name. Region, logging, networking, and storage settings specified here take precedence over s.yaml. For example, if s.yaml specifies China (Hangzhou) but the environment is set to China (Beijing), resources deploy to China (Beijing).
   Pipeline Configurations	Each environment maps to one pipeline by default. Configure the pipeline trigger and build steps here.

View environment details

1. Log on to the Function Compute console.

2. In the left-side navigation pane, click Applications.

3. On the Applications page, find your application and click the expand icon on the left side to list its environments.

4. Click an environment name to open the Environment Details tab. The tab displays: This tab also provides access to cloud-based development and pipeline configuration.

   • Basic information

   • Code source configurations

   • Deployment History

   • Resources

Roll back an environment

A rollback redeploys the code and resource configurations (for example, the s.yaml file) captured in the snapshot of a previous deployment.

1. Open the Environment Details tab for the target environment.

2. In the Deployment History section, click Roll Back next to the deployment you want to restore.

Manage resources

Serverless Application Center displays resource binding information in read-only mode. To manage resources, use the s.yaml file in your code repository rather than changing settings directly on the resource management page.

Develop in the cloud

1. On the application details page, click Cloud Development.

2. Click Initialize Code Repository to set up the code environment.

3. After initialization, use WebIDE to view, edit, and debug code.

4. Push changes to the repository using one of the following methods:

   • Use the built-in terminal or Git plug-in.

   • Click Save Code to Repository in the upper-left corner to add, commit, and push in one step.

Configure pipelines

For details on pipeline configuration, see Manage pipelines.

Delete an environment

1. Log on to the Function Compute console.

2. In the left-side navigation pane, click Applications.

3. Find the environment to delete and click Delete in the Actions column.

4. In the confirmation dialog, review the listed resources. Clear the check boxes next to any resources you want to keep.

Isolate services across environments

Serverless Application Center follows a GitOps model: Git repositories are the single source of truth for application state, and a YAML file that follows the Serverless Devs YAML specification drives deployments.

In many enterprise settings, R&D and O&M roles have distinct responsibilities. O&M teams manage infrastructure and authorize developers to use it. R&D teams manage application code. If all infrastructure is maintained in a Git repository, O&M personnel must submit code to change the infrastructure, which conflicts with the workflow of most O&M engineers. The following deployment methods address this separation at different scales.

Method 1: Separate YAML files per environment

Maintain a dedicated YAML file for each environment and point each pipeline to its corresponding file.

To reduce duplication across YAML files, use YAML inheritance in Serverless Devs.

vars:
  region: ${env(region)}
  service:
    name: demo-service-${env(prefix)}
    internetAccess: true
    logConfig:
      project: ${env(LOG_PROJECT)}
      logstore: fc-console-function-pre
    vpcConfig:
      securityGroupId: ${env(SG_ID)}
      vswitchIds:
        - ${env(VSWITCH_ID)}
      vpcId: ${env(VPC_ID)}

service:
  logConfig:
    project: ${environment.outputs.slsProject}
    logstore: ${environment.outputs.slsLogStore}
  vpcConfig:
    vpcId: ${environment.outputs.vpcId}
    securityGroupId: ${environment.outputs.securityGroupId}
    vswitchIds:
    - ${environment.outputs.vswitchId}
  nasConfig:
    userId: 10003
    groupId: 10003
    mountPoints:
    - serverAddr: ${environment.outputs.nasMountTargetId}
      nasDir: /fc-deploy-service
      fcDir: /mnt/auto

References

• Manage pipelines

• Serverless Devs YAML specification

• YAML inheritance in Serverless Devs

• <code data-tag="code" class="inline-code___exakR" id="code_14d2ec6a">customDomains</code> configuration