What is Solodev Buildspec?

Solodev Buildspec is a specialized set of build commands and settings for creating custom forms. With Buildspec, users can define form fields, capture form answers, and provide values for specific applications. It utilizes clear and simple YAML syntax and is being used in various places in the Solodev Cloud.

For example, users with a Marketplace Seller subscription can use Buildspec to customize their forms – allowing them to define the questions they need to ask buyers when configuring services in the Soldev Store. They can also use Buildspec to collect and pass values for various parameters in AWS CloudFormation Templates.

Anywhere that questions need to be asked – or answers provided – Buildspec can be used to customize a form and capture the necessary information.

Forms

Using the form param, you can define your form with all its required fields. The basic structure of the content follows this format:

form: // beginning the form definition section
- id: {name} // unique identifier of the field
type: {field_type} // type of the field
label: {Some Label} // label connected with this field
description: {Test description for the name field} // helper text displayed under the label
required: {true|false} // requirement flag
autofocus: {true|false} // this field will gain focus right after the page load
hideLabel: {true|false} // if you need to turn off the label
placeholder: {Placeholder text} // useful with input or dropdown fields
- id: {name}
...

Field Types

The type section lets you control how specific form questions are formatted in the UI as well as the kind of responses that are expected or required.

For more details on managing field types and the available formats, click here.

Builds

Using the build param, you can provide default values for questions asked in Cloud Formation Templates. The basic structure of the param looks like this:

build: // beginning of the build section
- ParameterKey: AppVersion // key of the parameter
ParameterValue: latest // value of the paramter
- ParameterKey: DatabasePassword
...

The build section currently has only two subsections but can handle almost anything new that will be needed in the future. To add value to any parameter in the CFT, you only need to provide its key – so the parameter and the value can be matched during the build.

Did this answer your question?