2. what I notice is that I have chainsaw tests perfectly working and not flickering in my local machine but in GHA they flicker, probably because of resource constraints or something. I use devbox to run tests so I doubt is because of installed packages.

1. Yes I could write kcl code which outputs valid chainsaw yaml, but that's not what I meant. If you have a look at github.com/upbound/conf... for example you don't see any trace of chainsaw language, no bindings, no templates This translation layer from kcl to chainsaw testing is done by upbound.

So what I'm trying to say is that with chainsaw I face 2 problems
1. I have to write tests in chainsaw language instead of kcl
2. I sometimes see chainsaw tests flickering on GitHub actions, I thought it could be better adopting upbound tooling for this

Yes but from the user perspective this is hidden since you write tests using kcl like in the composition itself

@vfarcic.bsky.social thank you for the answer. And what about assigning crossplane.io/external-name ? Is that a good practice to always assign it to have deterministic external resources names?

@vfarcic.bsky.social No problem! I booked a timeslot on the December 11 if it's ok for you

Hi @vfarcic.bsky.social thank you again for your time.
I managed to fix the issue with Chainsaw by using a different approach based on a simple ConfigMap. If you're interested I'm happy to share the solution I came up with on another call

Thank you @vfarcic.bsky.social |! Talk to you tomorrow