...
The build workflow is only going to need two steps: clone the source code and build the image. The buildProjectImage buildImage step is going to use the configuration directly in the done with project properties. As such, the default configuration is is fine for both steps, simply drag and drop.
...
Head back to the Project Activity Screen and click the deploy button. If everything goes well there will be a new successful deployment of the Helm Release.
...
You may notice a few things that stand out compared to other FlexDeploy Projects, namely the Deployment link and Status. Both of these are shown for Container Projects only and offer some insight into the actual application that was deployed and some basic monitoring.
...
FlexDeploy supports native Anchore inline image scanning. What this means for you is that no additional installations or setup is needed apart from updating our the Project configuration.
| Warning |
|---|
At this time, inline(local) image scanning is not supported on windows |
Updating the Project Image Scanning Configuration
Navigate back to the Container Configuration tab on the Project. Under the Image Scanning section, change the Scan Image drop down to Before Push and set the Fail When script to
STATUS == “fail”.
...
We have just told FlexDeploy to run an Anchore scan prior to pushing our image and if the scan Status is “fail” then the build will fail. Save the changes and run another build. If you are using the natours repository, the build will now fail due to the scan results.
...