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

[Submission Pipeline] Create modulectl-create script and reference it in the workflow #154

Open
4 tasks
nesmabadr opened this issue Feb 4, 2025 · 0 comments

Comments

@nesmabadr
Copy link
Contributor

Description

Create a modulectl-create script in the test-infra/ado/scripts to run the modulectl create command handling all the changes that were introduced in the modulectl according to the migration guide. Also it needs to support the check only without pushing to the registry (using the --dry-run flag) similar to the script kyma-alpha-create-module.sh.

The moduleTemplate generated should follow a new name which is "moduletemplate-- and the location should be in the Kyma-modules repo but under kyma-modules/{modulename}/{moduletemplate-modulename-version.yaml}. This change also needs to be documented in the Kyma-modules repo instead of having them organized by the release channels.

It should be referenced in the test-infra/templates/submission-workflow.yaml if the result of the decide-if-modulectl-command is true, once for the validation and the other time for the module creation. Check the kyma_alpha_create_module and validate_module_changes as a reference.

Reasons

We need to migrate from Kyma-cli to modulectl create command

ACs

  • Create modulectl-create script, covering all modulectl features as well as the --dry-run
  • Reference it in the submission-workflow for validation
  • Reference it in the submission-workflow for module creation
  • Change the Kyma-modules repo documentation to reflect the new folder structure
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