Nic Cope
Implementation wise I think it might be possible to do this using a `generate.WriteOption`. Something like: ```go err := generate.WriteMethods(p, methods, filepath.Join(filepath.Dir(p.GoFiles[0]), filename), generate.Satisfies(i), // i is however we choose...
Bumping this. Having to figure this image out every time I want to try out a new linkerd release demotivates me from doing so.
Thanks! It would be super cool to have OpenJ9 variants published too if this is something you're automating. :)
@jirfag Ping. Is this something that is already open source?
Thanks for working on this @pdettori!
@jbw976 is correct here - the trick is to run `sonobuoy delete --wait` after each run to cleanup per https://github.com/vmware-tanzu/sonobuoy#getting-started
I just took an initial pass at running the conformance tests for provider-aws. Looks like there there are a whole bunch of non-conformant CRDs, but at a glance most of...
Here's another test run, in this one I just applied the `examples/` directory of provider-aws to quickly determine which resources spun up successfully and became healthy: Test results ``` ===...
I believe once we fix https://github.com/crossplane/provider-aws/issues/697 we'll just need to verify that all managed resources can become Ready and pass their tests. We know the following 34 managed resources are...
@hasheddan @turkenh @muvaf @aaronme @ulucinar If I recall correctly there's 35 resources that didn't pass in my comment above. Could each of you pick 7 resources to test and comment...