Customer can create a WebExperience without setting AuthConfiguration. In this case, the resource will be in "PENDING_AUTH_CONFIG" status after creation. If customer update WebExperience and also does not provide AuthConfiguration, we should let the update succeed if status is "PENDING_AUTH_CONFIG". In the current UpdateHandler, resource is stabilized only if status becomes "ACTIVE"
Description of changes:
Update WebExperience UpdateHandler stabilizer to return true if "AuthConfiguration" is null and status is "PENDING_AUTH_CONFIG"
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.