Skip to content
This repository was archived by the owner on Mar 14, 2024. It is now read-only.

Packaging

Jump to bottom
glechev edited this page Jun 30, 2021 · 1 revision

Packaging

vRealize Automation Content Generator code can be packaged and distributed in several different ways depending on the use case.

  • Plain files / archive - good for small project or when you want to share a single piece of configuration. The consumer can then
  • Docker container - good for sharing a ready-to-use content package. For this you'll need to extend the provided image from CLI Container as execution platform or create one from scratch.
  • Project - good for development and maintenance of content as it can be stored under SCM. This can be any project format you like, the recommended format is Maven.
Clone this wiki locally