Fix ApigeeEnvironment update response type. #12415
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the
ApigeeEnvironment
update response type according to the public documentation.The issue is related to the fact that after requesting the update to
ApigeeEnvironment
here, the provider expects that the response will contain the Operation details to then wait for theOperation
to complete here. Unlike Environment create request, which returnsOperation
, the update response has a type Environment according to the public docs, meaning that the ApigeeOperationWaitTime tries to process theEnvironment
asOperation
.The Operation has a
name
key that is used to track its progress. However, theEnvironment
also has aname
key that contains the name of theEnvironment
. That's why the users may see a weirdapigee.googleapis.com/v1/<env-name>?alt=json
GET
requests that result in404 Not Found
while doing an update to their environments. In that case, theApigeeOperationWaitTime
interprets<env-name>
as the operation name.Here's a fix to a similar issue for the
ApigeeOrganization
: #12413Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.