Managing service deployment in a cloud computing environment

A device, comprising:

• one or more memory devices;
• and
• one or more processors, communicatively connected to the one or more memory devices, to:
• receive, from a user device, data identifying a service to be deployed in a cloud computing environment;
• receive, from the user device, data identifying an execution environment in which the service is to be deployed;
• receive, from the user device, data identifying a framework on which the service is to be deployed;
• receive, from the user device, data identifying a version strategy to be applied to the service,
• the version strategy including information designed to indicate how a version number associated with the service is to be changed, and
• the version strategy being associated with one of a plurality of version strategies,
• each of the plurality of version strategies causing determination of service version numbers in a different manner;
• receive, from the user device, data identifying a user account associated with the service;
• access data identifying permissions associated with the service,
• the permissions indicating at least one user account associated with permission to deploy the service;
• determine, based on the user account and the permissions, that the user account has permission to deploy the service;
• identify a service template based on the service,
• the service template specifying a virtual hardware configuration;
• and
• provide, to a service deployment platform, instructions to deploy the service using the virtual hardware configuration,
• the instructions including:
• the data identifying the execution environment,
• the data identifying the framework, and
• the data identifying the version strategy.

A non-transitory computer-readable medium storing instructions, the instructions comprising:

• one or more instructions that, when executed by one or more processors, cause the one or more processors to:
• receive data identifying a service to be deployed in a cloud computing environment;
• receive data identifying a version strategy to be applied to the service,
• the version strategy being associated with one of a plurality of version strategies, and
• each of the plurality of version strategies causing determination of service version numbers in a different manner;
• receive data identifying a user account associated with the service;
• access data identifying permissions associated with the service, the permissions indicating at least one user account associated with permission to deploy the service;
• determine, based on the user account and the permissions, that the user account has permission to deploy the service;
• identify a service template based on the service,
• the service template specifying a virtual hardware configuration;
• determine a version of the service based on the version strategy;
• and
• provide, to a service deployment platform, instructions to deploy the service using the virtual hardware configuration and the version.