The Murano project defines a specific structure that should be used to develop and successfully publish an application in the catalog container. As we have explored in the previous chapter, a Murano application is simply a deployable package that includes a set of files in a ZIP format. Once uploaded to the catalog service, Murano unzips the package and runs a series of checks on the structure and presence of predefined files that we would expect to be present at different levels.
A Murano application package should be organized as illustrated in the following hierarchical file tree:
Let's break down the file tree and briefly parse the definition of each folder and file that Murano expects when uploading the .zip file:
- manifest.yaml: This is a fixed file name that Murano expects as the first application entry point. The manifest file...