The OFO demo currently pulls in the latest (0.5.3) version of OFO, but uses deprecated CRs, so things don't work. The migrations here) should be applied to the CRs.

We should also lock the version of OFO used to a specific one, so that this doesn't happen again.

The current nohup port-forward command in the operator tutorial is unreliable.

Move this to a user-activated port-forwarding as a 502 at initial startup is not a good look & can lead to the user thinking it's broken and not progressing.

Update the flagd version in flagd tutorial from 0.4.4 to 0.4.5

The OFO tutorial still uses 0.4.0, update to 0.6.3

https://github.com/open-feature/playground/releases/tag/v0.6.3

Multiple links within https://github.com/open-feature/killercoda/blob/main/openfeature-demo/step1.md do not exist anymore.

i tried to locate them within the playground but did not find them eg hex-color.service.ts

The killercoda Operator tutorial is outdated and broken. Thanks @salaboy who made me realise this.

1. Helm chart is now open-feature/open-feature-operator not open-feature/ofo
2. Need kubectl create namespace open-feature-demo
3. kubectl apply end-to-end.yaml needs a namespace added
4. Need to create a standlone featureflagconfiguration for two reasons: 1) It makes editing more logical. 2) kubectl applying end-to-end fails as it contains the service which is already bound to port 30000.
5. Move the port-forwarding to a nohup operation in the creation script

In short, this issue will fix the OpenFeature operator Killercoda tutorial and bring it up to date.

Currently the openfeature-demo tutorial (https://bit.ly/openfeaturedemo) git clones the HEADofmain`.

To allow main to be used without fear of updates breaking the demo, the tutorial should be pinned to a particular tag - updates will then be done by updating the tag as new playground apps come out.

This will give devs the confidence to push to main and know they aren't going to break the demo applications.

How?

Change:

git clone https://github.com/open-feature/playground
cd playground

to:

git clone https://github.com/open-feature/playground
cd playground
git fetch --all --tags
git checkout tags/v0.6.3

Where?

https://github.com/open-feature/killercoda/blob/main/openfeature-demo/assets/scripts/foreground.sh

I've implemented the lambda tracking but Killercoda isn't syncing the latest.

Spoken to killercoda support and they see the drift too. The live version isn't what is in GitHub. ie. The lambda calls aren't actually live yet.

This leads me to believe the webhook in the GitHub repos isn't firing.

Killercoda says:

The version ucrrently active on Killercoda seems not to be the latest one when comparing to Github. Profile says "Last updated at 2023-03-22 02:27:31 UTC". There are no errors for the repository pdates.

Best would be to log into the Killercoda account and hit the "webhook call" button.

Problem: I am not able to log into the OpenFeature GitHub account to diagnose this further. Mike, can you add me or do the above?

The end-to-end.yaml file somehow got misplaced during #7. Re-add it.