Details
-
New Feature
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
As of mailing discussions and BEAM-5187, it has become clear that we need to extend the Environment information. In addition to the Docker environment, the extended environment holds deployment options for 1) a process-based environment, 2) an externally managed environment.
The proto definition, as of now, looks as follows:
message Environment { // (Required) The URN of the payload string urn = 1; // (Optional) The data specifying any parameters to the URN. If // the URN does not require any arguments, this may be omitted. bytes payload = 2; } message StandardEnvironments { enum Environments { DOCKER = 0 [(beam_urn) = "beam:env:docker:v1"]; PROCESS = 1 [(beam_urn) = "beam:env:process:v1"]; EXTERNAL = 2 [(beam_urn) = "beam:env:external:v1"]; } } // The payload of a Docker image message DockerPayload { string container_image = 1; // implicitly linux_amd64. } message ProcessPayload { string os = 1; // "linux", "darwin", .. string arch = 2; // "amd64", .. string command = 3; // process to execute map<string, string> env = 4; // environment variables }