Library Assets

Assets are identified by filename patterns and are read from the library member directories. The assets are processed according to their names, the directory they are in is not considered, however you may wish to organize your files in to directories for clarity. The name (JSON property .name) of the asset must be unique for any given asset type. For example, you cannot have two policy definitions with the same name. This is especially important when considering extensibility. Assets are keyed by name, during the process of creating a deployable architecture, the assets are modified to update references such as resource ids. Clients should lookup references resources by name and correctly update values before deploying the resource.