What are the guidelines to create and upload the manifest files? - Manual - Developer Cockpit for Subscribers to MindAccess Plans - The developers can create and manage applications within the platform and use various services. The Industrial IoT capability packages excludes Cloud Foundry compute resources for developing applications using various capabilities packs. - Industrial Operations X - Insights Hub - MindAccess Plans - Developer Cockpit - Cloud-based application

Rules to create and upload a manifest file:

For uploading a manifest file, the following factors should be considered:

• The "name" parameter in "manifest.yml" should match the name entered in the "Components" section.
• The "path" parameter in "manifest.yml" should point to the correct file/ files.
• The "path" parameter in "manifest.yml" file should be as per the folder structure.
• Do not use the following parameters in the manifest file as they are deprecated:
  • domain
  • domains
  • host
  • hosts
  • no-hostname
  • Use of 'buildpacks' attribute in manifest is not fully supported. Hence use of 'buildpack' is favored. The feature will be updated in future.
• It is recommended to use random-route: true to avoid path conflicts.
• If a user wants to specify routes for an application, the user has to use routes attribute.

Example scenario to upload manifest files:

The manifest file has the following structure with "buildpack":

① Manifest with random-route: true and path corresponding to zipping structure

② Manifest with random-route: false and with specified routes and path corresponding to zipping structure