Curated image management in a FaaS infrastructure

A non-transitory computer readable storage medium having stored thereon program code executable by a computer system in a Functions-as-a-Service (FaaS) infrastructure, the program code embodying a method for implementing curated image management in the FaaS infrastructure, the method comprising:

• presenting, to an application developer via a first user interface (UI), one or more curated base images defined by one or more administrators of the FaaS infrastructure, each of the one or more curated base images comprising an operating system and a language runtime;
• receiving, from the application developer, a selection of a curated base image from among the one or more curated base images via the first UI;
• presenting, to the application developer via the first UI, one or more curated software lists, the one or more curated software lists identifying curated software components that have been previously:
• approved by the one or more administrators for use on the FaaS infrastructure;
• and
• associated by the one or more administrators with the selected curated base image;
• receiving, from the application developer, a selection of a curated software component from the one or more curated software lists;
• generating a custom image, the custom image being an executable package of files that incorporates the selected curated software component and the selected curated base image;
• subsequently to generating the custom image, receiving, from the application developer, a function artifact including program code for a function;
• in response to receiving the function artifact, presenting, to the application developer via a second UI, a set of custom images previously generated in accordance with selections made by the application developer via the first UI, the set of custom images including the custom image;
• receiving, from the application developer, a selection of the custom image from among the set of custom images via the second UI, the custom image including software dependencies for the function;
• and
• generating a function runtime image that incorporates the function artifact and the custom image, the function runtime image being useable for running the function on the FaaS infrastructure.

A computer system comprising:

• a processor;
• and
• a non-transitory computer readable medium having stored thereon program code that, when executed by the processor, causes the processor to:
• present, to an application developer via a first user interface (UI), one or more curated base images defined by one or more administrators of the FaaS infrastructure, each of the one or more curated base images comprising an operating system and a language runtime;
• receive, from the application developer, a selection of a curated base image from among the one or more curated base images via the first UI;
• present, to the application developer via the first UI, one or more curated software lists, the one or more curated software lists identifying curated software components that have been previously:
• approved by the one or more administrators for use on the FaaS infrastructure;
• and
• associated by the one or more administrators with the selected curated base image;
• receive, from the application developer, a selection of a curated software component from the one or more curated software lists;
• generate a custom image, the custom image being an executable package of files that incorporates the selected curated software component and the selected curated base image;
• subsequently to generating the custom image, receive, from the application developer, a function artifact including program code for a function;
• in response to receiving the function artifact, present, to the application developer via a second UI, a set of custom images previously generated in accordance with selections made by the application developer via the first UI, the set of custom images including the custom image;
• receive, from the application developer, a selection of the custom image from among the set of custom images via the second UI, the custom image including software dependencies for the function;
• and
• generate a function runtime image that incorporates the function artifact and the custom image, the function runtime image being useable for running the function on the FaaS infrastructure.