Add asset generation tests

[aufi]

There is a new asset-generation feature being added to kantra in konveyor/kantra#435

E2E test scenarios should be defined, approved, written as part of this repository.

Selected subset of those tests should be marked as TIER0 and added to upstream CI execution.

[jordigilh]

Test 1:

• Objective:
  Test the discovery and generation of K8s manifests using the kantra CLI with a helm chart that only contains K8s manifests.

• Prerequisites:

  • Local copy of PCF V3 manifest as defined here: https://raw.githubusercontent.com/gciavarrini/demo-kantra-asset-gen/refs/heads/main/cf-nodejs-app.yaml to ./cf-nodejs-app.yaml
  • Local copy of helm chart in https://github.com/gciavarrini/demo-kantra-asset-gen/tree/main/helm_sample to ./helm_sample
  • Kantra CLI with the generate and discover subcommands supporting PCF V3

• Steps:

(1) Run command: kantra discover cloud-foundry --input ./cf-nodejs-app.yaml --output discover.yaml
(2) Validate that the generated file contains the following content:

name: cf-nodejs
randomRoute: true
timeout: 60
buildPacks:
- docker://my-registry-a.corp/nodejs
- docker://my-registry-b.corp/dynatrace
instances: 1

(3) Run command kantra generate helm --chart-dir ./helm_sample --input discover.yaml --output-dir ./manifests
(4) Validate the generated file in ./manifests matches the expected value:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cf-nodejs-config
data:
  SPACE:
  VERSION:
  RANDOM_ROUTE: true
  TIMEOUT: "60"
  BUILD_PACKS: |
    - docker://my-registry-a.corp/nodejs
    - docker://my-registry-b.corp/dynatrace
  INSTANCES: "1"

[jordigilh]

Test 2

• Objective:
  Test the discovery and generation of the non-K8s manifests using the kantra CLI with a helm chart that only contains non-K8s manifests.
• Prerequisites:
  • PCF V3 application manifest with at least required fields as specified by the PCF application specification
  • Helm chart containing helm templates for non-K8s (not yaml or json format) stored inside of files/konveyor. These templates should include references to the keys in the discover manifest as generated by the kantra discover cf command.
  • Kantra CLI with support for asset generation commands for PCF V3

Steps:
(1) Run command: kantra discover cloud-foundry --input ./<name of the PCF application manifest> --output discover.yaml
(2) Validate that the generated file contains the expected output, as defined by the discover enhancement specification
(3) Run command: kantra generate helm --non-k8s-only --chart-dir <location of the helm chart> --input discover.yaml --output-dir ./manifests
(4) Validate that the generated file(s) in the ./manifests match the expected content.

[nachandr]

Hi @jordigilh , @dymurray, @rromannissen,

I see that Jordi has added a test case for generating non-k8s manifests . Is supporting non-k8s target platforms a long term goal?

cc @istein1

[rromannissen]

@nachandr it is an immediate goal and priority.

[dymurray]

@nachandr specifically we see Dockerfiles as being a common use case for this; so good to include that in our tests