SecOpsCentral

How images are released

Every image is built from a recorded recipe on a clean machine, so a release can be reproduced.

Release flow: recipe, clean build, real launch, automated tests, cleaning, publish; a failed check stops the release.1Recorded recipeversioned, reproducible2Clean buildfresh machine3Real launchno manual steps4Automated testsserve and refuse5Cleanedno build leftovers6Publishedunique credentialsany check failsNot publishedRelease flow: recipe, clean build, real launch, automated tests, cleaning, publish; a failed check stops the release.1Recorded recipeversioned, reproducible2Clean buildfresh machine3Real launchno manual steps4Automated testsserve and refuse5Cleanedno build leftovers6Publishedunique credentialsNot published

If any check fails, the release is not published.

Before an image is published it is launched on a real instance and tested: it must start with no manual steps, serve what it should, and refuse what it should. A release that fails any check is not published.

Images are cleaned before they are saved: no keys, credentials or history from the build remain, and each instance generates its own credentials on first launch.

We list what each image adds beyond a default installation. We do not publish how it is configured.