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.

Sign up for GitHub

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

Jump to bottom

Release the Module Template and Manifest #52

Closed
5 tasks done
janmedrek opened this issue Apr 28, 2023 · 7 comments
Closed
5 tasks done

Release the Module Template and Manifest #52

janmedrek opened this issue Apr 28, 2023 · 7 comments
Assignees
@LeelaChacha
Labels
area/ci Issues or PRs related to CI related topics

Comments

@janmedrek
Copy link
Contributor

janmedrek commented Apr 28, 2023 •
edited by LeelaChacha
Loading

Description

It would be great to have the Module Template and manifest (k8s yamls) released for the Template Operator. It will make it easier to present/use the example in various tutorials, documents, or guides.

Keda Manager, BTP Manager and eventing-manager already have their pipelines built, this can be a starting point for this implementation.

Acceptance Criteria

  • GH actions pipeline built
  • ModuleTemplate available in GH release (0.1.2)
  • Default CR available in GH release (0.1.2)
  • K8S manifests available in GH release (0.1.2)
  • (stretch) include module-config file for the CLI build command

Reasons

It will be much easier to just download the Module Template and Manifest instead of building it locally.
@janmedrek janmedrek added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Apr 28, 2023
@kyma-bot
Copy link
Contributor

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 27, 2023
@kyma-bot
Copy link
Contributor

kyma-bot commented Jul 4, 2023

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

@kyma-bot kyma-bot closed this as completed Jul 4, 2023
@kyma-bot
Copy link
Contributor

kyma-bot commented Jul 4, 2023

@kyma-bot: Closing this issue.

In response to this:

This issue or PR has been automatically closed due to the lack of activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle stale

If you think that I work incorrectly, kindly raise an issue with the problem.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@janmedrek janmedrek removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2023
@janmedrek janmedrek reopened this Jul 6, 2023
@janmedrek janmedrek changed the title Expose the Module Template and Manifest Release the Module Template and Manifest Aug 3, 2023
@kyma-bot
Copy link
Contributor

kyma-bot commented Oct 2, 2023

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 2, 2023
@janmedrek janmedrek removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2023
@lindnerby lindnerby self-assigned this Nov 8, 2023
@lindnerby lindnerby linked a pull request Nov 9, 2023 that will close this issue
feat: Add release workflow dispatch #117
Merged
@lindnerby lindnerby mentioned this issue Nov 9, 2023
Merged
@lindnerby lindnerby removed a link to a pull request Nov 13, 2023
feat: Add release workflow dispatch #117
Merged
This was referenced Nov 13, 2023
Merged
Closed
@lindnerby lindnerby mentioned this issue Nov 27, 2023
Merged
kyma-bot pushed a commit that referenced this issue Nov 29, 2023
@lindnerby
feat: Add make targets for asset upload (#129)
14e1bbb 
<!-- Thank you for your contribution. Before you submit the pull
request:
1. Follow contributing guidelines, templates, the recommended Git
workflow, and any related documentation.
2. Read and submit the required Contributor Licence Agreements
(https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md#agreements-and-licenses).
3. Test your changes and attach their results to the pull request.
4. Update the relevant documentation.

If the pull request requires a decision, follow the [decision-making
process](https://github.com/kyma-project/community/blob/main/governance.md)
and replace the PR template with the [decision record
template](https://github.com/kyma-project/community/blob/main/.github/ISSUE_TEMPLATE/decision-record.md).
-->

**Description**

Changes proposed in this pull request:

- add usage of kyma cli to create module and upload it
- fix module-template name and usage of registry

**Related issue(s)**
* #52
<!-- If you refer to a particular issue, provide its number. For
example, `Resolves #123`, `Fixes #43`, or `See also #33`. -->
@lindnerby lindnerby mentioned this issue Dec 5, 2023
Merged
kyma-bot pushed a commit that referenced this issue Dec 5, 2023
@lindnerby
chore: Set new versions for release (#132)
3aa9dfe 
<!-- Thank you for your contribution. Before you submit the pull
request:
1. Follow contributing guidelines, templates, the recommended Git
workflow, and any related documentation.
2. Read and submit the required Contributor Licence Agreements
(https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md#agreements-and-licenses).
3. Test your changes and attach their results to the pull request.
4. Update the relevant documentation.

If the pull request requires a decision, follow the [decision-making
process](https://github.com/kyma-project/community/blob/main/governance.md)
and replace the PR template with the [decision record
template](https://github.com/kyma-project/community/blob/main/.github/ISSUE_TEMPLATE/decision-record.md).
-->

**Description**

Changes proposed in this pull request:

- Test next release 0.1.1

**Related issue(s)**
* #52
@kyma-bot
Copy link
Contributor

kyma-bot commented Jan 7, 2024

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale

@kyma-bot kyma-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2024
@janmedrek janmedrek removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 8, 2024
@lindnerby lindnerby added area/ci Issues or PRs related to CI related topics and removed good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jan 29, 2024
@LeelaChacha LeelaChacha self-assigned this Feb 11, 2024
@LeelaChacha LeelaChacha mentioned this issue Feb 11, 2024
Merged
@LeelaChacha LeelaChacha removed their assignment Feb 11, 2024
@LeelaChacha LeelaChacha mentioned this issue Feb 11, 2024
Merged
@jeremyharisch jeremyharisch self-assigned this Feb 12, 2024
kyma-bot pushed a commit that referenced this issue Feb 12, 2024
@LeelaChacha
fix: Selecting Kyma CLI Binary Based on OS (#151)
3514da7 
**Related issue(s)**
<!-- If you refer to a particular issue, provide its number. For
example, `Resolves #123`, `Fixes #43`, or `See also #33`. -->
Fixes the problem in #52
kyma-bot pushed a commit that referenced this issue Feb 12, 2024
@LeelaChacha
fix: Asset Uploading (#152)
a37bfb1 
<!-- Thank you for your contribution. Before you submit the pull
request:
1. Follow contributing guidelines, templates, the recommended Git
workflow, and any related documentation.
2. Read and submit the required Contributor Licence Agreements
(https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md#agreements-and-licenses).
3. Test your changes and attach their results to the pull request.
4. Update the relevant documentation.

If the pull request requires a decision, follow the [decision-making
process](https://github.com/kyma-project/community/blob/main/governance.md)
and replace the PR template with the [decision record
template](https://github.com/kyma-project/community/blob/main/.github/ISSUE_TEMPLATE/decision-record.md).
-->

**Description**

Changes proposed in this pull request:

- Fix the selection of Kyma CLI (this will fix the asset uploading Prow
Job)
- Set Version to 0.1.2 to enable new release

**Related issue(s)**
<!-- If you refer to a particular issue, provide its number. For
example, `Resolves #123`, `Fixes #43`, or `See also #33`. -->
Closes #52
@LeelaChacha
Copy link
Contributor

0.1.2 released with the assets mentioned in the issue

@jeremyharisch
Copy link
Contributor

https://github.com/kyma-project/template-operator/releases/tag/0.1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LeelaChacha LeelaChacha

Labels
area/ci Issues or PRs related to CI related topics
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@janmedrek @kyma-bot @jeremyharisch @lindnerby @LeelaChacha