Skip to content

Lack of tagged versions causes trouble for provider development #58

Description

@peterlindsten

What happened?

Naive provider from scratch development flow breaks when using @latest version of both crossplane-runtime and crossplane-tools, due to managed interface no longer being satisfied.
#57 is the the breaking point, using older revsion 2684f4b works fine.

I expected there to be a (tagged) version of crossplane-tools to be compatible with the "current" version of crossplane-runtime

How can we reproduce it?

Clone https://github.com/crossplane/provider-template
Update dependencies to @latest
Ensure you have a resource API to be managed (in apis/)
make generate
Error manifests in zz_generated.managedlist.go for not satisfying the managed interface

What environment did it happen in?

Crossplane version:
crossplane-runtime 1.13 (current @latest)
crossplane-tools 628280f (current @latest)
Go 1.21

Suggested fix

Tag crossplane-tools 2684f4b with 0.1.0 or similar

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions