• TestAccDocumentAIProcessorDefaultVersion_documentaiDefaultVersionExample
  Google Cloud - 100% failure
  Google Cloud Beta - 100% failure

b/261553942

Could likely resolve this with projectNumberDiffSuppress

projectNumberDiffSuppress is already in use. The issue is actually that pretrained-next is being replaced with pretrained-ocr-v1.0-2020-09-23. This is due to a change in how model versions are managed - that naming scheme is no longer in use. There are now release channels instead, like projects/my-proj/locations/us/processors/my-processor/processorVersions/stable. Using the release channels directly would have the same permadiff behavior observed with pretrained-next.

We should probably suppress the diff, though I think there's a risk that folks will end up in a state where they don't see there's a new version of the release branch available.

We could also consider something like https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/container_engine_versions to allow querying available processor versions. The DocumentAI API only allows listing available versions within a particular processor, so it's convenient that the default version resource is separate - we could have a datasource that reads available versions for the processor and feeds them as input to the default version resource.

There doesn't seem to be a way to determine whether a particular version is rc or stable, so I think it's currently not possible to make a datasource that would spit out the latest stable version.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.