When creating a bucket or entry that was previously in terraform state but has been deleted in nats, the provider would error instead of trying to create either the bucket or entry again as expected in terraform. This was due to incorrectly handling the non-exist case in the respective read functions. This behaviour now matches that of streams/consumers.
ripienaar
commented
1 year ago
When creating a bucket or entry that was previously in terraform state but has been deleted in nats, the provider would error instead of trying to create either the bucket or entry again as expected in terraform. This was due to incorrectly handling the non-exist case in the respective read functions. This behaviour now matches that of streams/consumers.