This PR continues on top of #665 and adds management of Solution Add-Ons within a Solution Landing Zone.
To create a Solution Add-on, one must have a Solution Add-On image. Due to the architecture of Solution Add-Ons it must be present both - locally and and also uploaded to the catalog.
A local copy is needed to extract the image and pick required metadata - such as icon, EULA, certificate and Add-On type, while a copy in the VCD catalog will be used to create Solution Add-On instances later.
Testing
Testing VCD environment is expected to have an image uploaded already to nsxtBackedCatalogName and name of it must be specified in nsxtCatalogAddonDse variable. The Test_SolutionAddOn test will automatically check if the image is present locally within /test-resources/cache subdirectory (which is also added to .gitignore) - if it is not found - it will download the file from VCD catalog as defined in nsxtCatalogAddonDse variable
This PR continues on top of #665 and adds management of Solution Add-Ons within a Solution Landing Zone.
To create a Solution Add-on, one must have a Solution Add-On image. Due to the architecture of Solution Add-Ons it must be present both - locally and and also uploaded to the catalog. A local copy is needed to extract the image and pick required metadata - such as icon, EULA, certificate and Add-On type, while a copy in the VCD catalog will be used to create Solution Add-On instances later.
Testing
Testing VCD environment is expected to have an image uploaded already to
nsxtBackedCatalogNameand name of it must be specified innsxtCatalogAddonDsevariable. TheTest_SolutionAddOntest will automatically check if the image is present locally within/test-resources/cachesubdirectory (which is also added to.gitignore) - if it is not found - it will download the file from VCD catalog as defined innsxtCatalogAddonDsevariableTested on 10.4.1 and 10.5.1