You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
793ea4c Update functionality of 404 responses from alks
26b1e2a update go client and change the way role not found returns
5008e19 Throw error if we get an error from go, otherwise check the exists field
Changes to error handling in alks_iamrole
Previous behavior: Any error coming back from alks when attempting to read a remote role would be treated as a roleNotFound. This would lead to the terraform provider thinking a role was non-existent if there was a timeout or other error in the backend.
New Behavior: Any error other then a 404 Role Not Found will result in erroring out of the plan or apply. Role not found will be treated as before, resulting in either erroring, or attempted re-creation depending on the attempted action.