ci: add example release logic

[aepfli]

No description provided.

[netlify]

✅ Deploy Preview for keptn-lifecycle-toolkit ready!

Name	Link
🔨 Latest commit	33a5acf
🔍 Latest deploy log	https://app.netlify.com/sites/keptn-lifecycle-toolkit/deploys/641c102d18eb210007832e14
😎 Deploy Preview	https://deploy-preview-1008--keptn-lifecycle-toolkit.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[codecov]

Codecov Report

Merging #1008 (f6a9402) into main (8608f11) will increase coverage by 0.06%.
The diff coverage is n/a.

❗ Current head f6a9402 differs from pull request most recent head 65d221d. Consider uploading reports for the commit 65d221d to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1008      +/-   ##
==========================================
+ Coverage   58.91%   58.98%   +0.06%     
==========================================
  Files         126      126              
  Lines       10007    10007              
==========================================
+ Hits         5896     5903       +7     
+ Misses       3893     3888       -5     
+ Partials      218      216       -2     

see 4 files with indirect coverage changes

Flag	Coverage Δ
certificate-operator	64.15% <ø> (ø)
component-tests	60.47% <ø> (-0.58%)	⬇️
lifecycle-operator	78.40% <ø> (ø)
metrics-operator	77.35% <ø> (ø)
scheduler	21.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[mowies]

I don't really understand what this pipeline is doing. Right now, from what I understand, it would copy the examples folder content from keptn/lifecycle-toolkit into ./tmp/examples in the keptn-sandbox/lifecycle-toolkit-examples repo and push that.
What's the reasoning behind that?

[aepfli]

I don't really understand what this pipeline is doing. Right now, from what I understand, it would copy the examples folder content from keptn/lifecycle-toolkit into ./tmp/examples in the keptn-sandbox/lifecycle-toolkit-examples repo and push that. What's the reasoning behind that?

the tmp/examples folder is a git checkout of the lifecycle-toolkit-examples, so we do push those into the root. We do have two checkouts in this pipeline :)

the problem is https://github.com/keptn/lifecycle-toolkit/blob/v0.6.0/.github/actions/update-documentation/scripts/update_docs.py#L52

this line was part of the old documentation release and ensured that the most reason example files are within the example repo.
With this pull request, we add the functionality back in here - but in a way, that is not hidden in another process - more visible.

As far as I am informed, we want to have the most recent examples ready to fork for people to play with.

[mowies]

Thanks for the explanation @aepfli !
I misunderstood the code apparently 😅

[mowies]

@aepfli i left some more comments. also, did you test the release pipeline in your fork? If not, please do so to show that the whole setup still works.

[aepfli]

@aepfli i left some more comments. also, did you test the release pipeline in your fork? If not, please do so to show that the whole setup still works.

i tested it, and it sadly works :( https://github.com/keptn-sandbox/lifecycle-toolkit-examples - used my token but it seems like i have more permissions in the keptn-sandbox. - https://github.com/aepfli/lifecycle-toolkit/actions/runs/4500288808/jobs/7919264663

[mowies]

should i revert the release in the examples repo? i think it's fine anyways since we needed it for KLT 0.7.0

[aepfli]

should i revert the release in the examples repo? i think it's fine anyways since we needed it for KLT 0.7.0

i took a look, and i think it is fine, i will delete the tag - we would have needed to commit this anyways :)

[aepfli]

with peribolos we also want to migrate this repository to the keptn org i think

[mowies]

ok. then you just need to signoff your last commit and this should be ready to merge

[aepfli]

i hate github.dev - it is cool an easy to do things in the browser, but not signing something automatically is really annoying :D

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[mowies]

LGTM!