Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use consistent fqdn for moduletemplate and update outdated moduletemplate file #1774

Open
2 tasks
ruanxin opened this issue Aug 13, 2024 · 0 comments
Open
2 tasks

Comments

@ruanxin
Copy link
Contributor

ruanxin commented Aug 13, 2024

Atm, we still have tests use outdated fqdn for kyma-project.io/template-operator moduletemplate, which makes tests difficut to understand and maintain.

e.g:

  1. in test:
    WithArguments(kcpClient, shared.FQDN, "kyma-project.io/template-operator").
  2. in outdated moduletemplate:

AC:

  • replace outdated moduletemplate which use kyma-project.io/template-operator
    - operator_v1beta2_moduletemplate_kcp-module.yaml is used for generate moduletemplate for integeration tests, it should be replaced with moduletemplate_template_operator_v1_regular.yaml
    - operator_v1beta2_moduletemplate_kcp-module-cred-label.yaml is used for testing oci-registry-cred label, update it with new ocm component descriptor (requires a push to oci registry)
    - operator_v1beta2_moduletemplate_kcp-module_updated.yaml is used here, replace it with moduletemplate which is used for e2e test for update test.
    - operator_v1beta2_moduletemplate_ocm.software.v3alpha1.yaml is for testing ocm schema v3alpha1, use kyma cli generate a new version with correct fqdn (requires a push to oci registry)
    - push newly generated artefacts
  • adjust tests which use kyma-project.io/template-operator, replace it with kyma-project.io/module/template-operator, define a const fqdn name for sharing the usage among tests.
@ruanxin ruanxin changed the title use consistent fqdn for moduletemplate use consistent fqdn for moduletemplate and update outdated moduletemplate file Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant