Coverage decreased (-0.09%) to 77.115% when pulling 0e8ffcb on kayrus:userdata-typo into a875273 on gophercloud:master.

Renaming userdata to user_data looks correct, but this PR is also introducing a feature where Gophercloud will encode the data on behalf of the user. I don't think we need to include that.

Build failed.

• gophercloud-unittest : SUCCESS in 3m 22s
• gophercloud-acceptance-test : FAILURE in 2h 18m 00s
• gophercloud-acceptance-test-ironic : SUCCESS in 45m 47s

@jtopjian create server opts struct method does encode user_data to base64 automatically:
https://github.com/gophercloud/gophercloud/blob/675de7268e2618a557195c92ac49d1cc6d5e0174/openstack/compute/v2/servers/requests.go#L230..L238

Build failed.

• gophercloud-unittest : SUCCESS in 3m 18s
• gophercloud-acceptance-test : FAILURE in 1h 40m 19s
• gophercloud-acceptance-test-ironic : SUCCESS in 27m 10s

create server opts struct method does encode user_data to base64 automatically:

Ahh right. I knew we had support for this, but similar to a few other legacy areas you've been catching, this is ripe for removal. I checked the Terraform provider and it looks like it's passing in a string... so it's leaning on Gophercloud's encoding capability.

Either way, let's keep the result as being encoded. It's not consistent, but IMO it's the right way for Gophercloud to handle it.