Rob E
Rob E
It looks like the `octopusdeploy_ssh_key_account` is not passing the environments configured on the desired state to the back end. Fixes: https://github.com/OctopusDeployLabs/terraform-provider-octopusdeploy/issues/255
Simple test confirming once a connection is established the service messaging layer is bi-directional
The user roles are not space scoped as is evident by the [api template in this file](https://github.com/OctopusDeploy/go-octopusdeploy/blob/6d642919c6ef7ffae594336193013a2842d1be0c/pkg/userroles/user_role_service.go#L19). Passing a spaceId in the `userRoles.Get` method is confusing to consumers and so...