403 error when running example about terraform-provider-prefect HOT 2 OPEN

Hey, thanks for the report, and for being an early adopter!

The provider is currently incomplete, and missing features that would make debugging easier (#42). It's also missing automated tests (#30) so it's possible that I broke this functionality without realizing it.

The only way to troubleshoot right now is to modify the source code to add logging, which is certainly not ideal. I'll look into this issue and get back to you.

from terraform-provider-prefect.

Hi Johnathan, thanks for the reply. I have zero experience in Go, but still I gave it a shot and managed to hack my way through it.

What I found out is that calls like the one below in the internal\provider\resources\work_pool.go file yielded objects that had empty ApiKey strings, not "inheriting" from the api.PrefectClient object that was part of the resource object.

client, err := r.client.WorkPools(model.AccountID.ValueUUID(), model.WorkspaceID.ValueUUID())

So I patched things up by explicitly passing on the ApiKey as an aditional argument to the client factory methods, such as

client, err := r.client.WorkPools(model.AccountID.ValueUUID(), model.WorkspaceID.ValueUUID(), r.client.ApiKey())

With that out of the way, I've been working on exposing additional resources, such as deployments and flows. It's not pretty, but it works. If you're in any way interested I can share it.

Best regards
Carlos Jourdan

from terraform-provider-prefect.