From 7a2c462b1fb77205dc9936a7d1be0e4d884f241b Mon Sep 17 00:00:00 2001 From: Ramon Perez Date: Wed, 22 Nov 2023 16:55:22 +0100 Subject: [PATCH] Bump to tnf v4.5.6 (#59) --- roles/cnf_cert/README.md | 2 +- roles/cnf_cert/defaults/main.yml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/roles/cnf_cert/README.md b/roles/cnf_cert/README.md index 101ddaff3..05a534899 100644 --- a/roles/cnf_cert/README.md +++ b/roles/cnf_cert/README.md @@ -12,7 +12,7 @@ tnf\_stage | "tests" tnf\_check\_commit\_sha | false | Flag that allows to check if the tnf image used is based on the same commit SHA than the repository cloned in this role. test\_network\_function\_repo | https://github.com/test-network-function/cnf-certification-test | Repository to download the tnf code. test\_network\_function\_src\_dir | undefined | If testing a cnf-certification-test PR, this variable will be injected from test-runner scripts (used in dci-pipeline and dci-openshift-agent projects) to refer to the file path where the code from the PR is placed in the jumphost, so that it can be used in cnf_cert role to build a new tnf container image based on that code -test\_network\_function\_version | v4.5.5 | CNF Cert Suite version downloaded. DCI App Agent supports from v4.4.0 till the latest stable version. HEAD version (in the main branch) can be also used, but it is not guaranteed a complete compatibility with the latest unstable changes. +test\_network\_function\_version | v4.5.6 | CNF Cert Suite version downloaded. DCI App Agent supports from v4.4.0 till the latest stable version. HEAD version (in the main branch) can be also used, but it is not guaranteed a complete compatibility with the latest unstable changes. test\_network\_function\_project\_name | cnf-certification-test | Directory name to look at on the tnf repo. tnf\_labels | `"common,telco,extended"` | List of [test suites](https://test-network-function.github.io/cnf-certification-test/test-spec/#available-test-specs) that are executed/skipped using labels. In particular, `tnf_labels` content must follow [these guidelines](https://onsi.github.io/ginkgo/#spec-labels), then dci-openshift-app-agent uses this string to run the tnf container with `-l` argument. Note that, when using labels, apart from using the tnf suite names as labels, you can also use, among others, `common` label to refer to non-Telco tnf suites, `telco` label to include Telco-related tests, `extended` to other Verizon-related tests, `faredge` to Far-Edge tests, and `preflight` to run preflight on tnf. See the [cnf-certification-test README](https://test-network-function.github.io/cnf-certification-test/test-container/#run-the-tests) for more information, and also, check [CATALOG.md](https://github.com/test-network-function/cnf-certification-test/blob/main/CATALOG.md) to see the list of test suites available with the label that corresponds to each of them. tnf\_config | tnf_config:
   - namespace: "{{ dci_openshift_app_ns }}"
   targetpodlabels: []
   targetoperatorlabels: []
   target_crds: []
   exclude_connectivity_regexp: ""
| A complex variable to define the configuration to be applied in CNF Cert Suite. See [this](../../samples/tnf_test_example) for more details about an example defining this variable.
* Testing multiple resources on different namespaces is supported. diff --git a/roles/cnf_cert/defaults/main.yml b/roles/cnf_cert/defaults/main.yml index 17913aff1..c1139388c 100644 --- a/roles/cnf_cert/defaults/main.yml +++ b/roles/cnf_cert/defaults/main.yml @@ -2,7 +2,7 @@ tnf_stage: "tests" tnf_check_commit_sha: false test_network_function_repo: https://github.com/test-network-function/cnf-certification-test -test_network_function_version: v4.5.5 +test_network_function_version: v4.5.6 test_network_function_project_name: cnf-certification-test tnf_labels: "common,telco,extended" # By default, tnf_config takes the dci_openshift_app_ns namespace as it is already created by dci-openshift-app-agent, @@ -20,7 +20,7 @@ tnf_image_suffix: "{{ lookup('community.general.random_string', length=16, speci # Provide feedback for each tnf test launched. Just copy this template in your pipeline file and fill the value for the # tests you want to provide feedback. You don't need to include the tests that you don't want to provide feedback. # To insert line breaks, use \\n (you need to escape it). Same for quotes and so on. -# List of tests updated until tnf v4.5.5 +# List of tests updated until tnf v4.5.6 tnf_feedback: access-control-bpf-capability-check: "" access-control-cluster-role-bindings: ""