Added support for data_serviceendpoint_kubernetes

[muresan]

All Submissions:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran lint checks locally prior to submission.
• Have you checked to ensure there aren't other open PRs for the same update/change?

I did not see tests added to the other data sources, so I did not add one for this one.

The linked issue has info about this PR

What about the current behavior has changed?

Issue Number: #877

Does this introduce a change to go.mod, go.sum or vendor/?

• Yes
• No

Does this introduce a breaking change?

• Yes
• No

Any relevant logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Other information

[muresan]

@microsoft-github-policy-service agree

[xuzhang3]

@@muresan Thank you for your contribute. Can you help add AccTest to cover the new data source. And add separate schema(data source properties are simply compute=true) and flatten function for data source not simply reuse the resource functions.

[muresan]

@@muresan Thank you for your contribute. Can you help add AccTest to cover the new data source. And add separate schema(data source properties are simply compute=true) and flatten function for data source not simply reuse the resource functions.

Thank you for your comment. I added the kubernetes service endpoint in the same way as the sonar cloud service endpoint was added. Can you give me an example of another data source that I should follow ? All service endpoints data sources are added in the same way.
As for tests, can you point me to an example ? All the other serivice endpoint data souces had no tests so my assumption was that they are not desired. Can you point me to an example ?

Thanks.

[xuzhang3]

@muresan Data source only need the required parameter to get the service connection, other properties are not required. In the scenario, you are using the common schema for the k8s service connection. This is OK as the common schema cover the minimal properties requirement. You can add the same properties as azuredevops_serviceendpoint_kubernetes and all these properties are computed=true
Example:

r.Schema["service_account"] = &schema.Schema{
		Type:     schema.TypeList,
		MaxItems: 1,
		Computed: true,
		Elem: map[string]*schema.Schema{
			"ca_cert": {
				Type:     schema.TypeString,
				Computed: true,
			},
			"token": {
				Type:     schema.TypeString,
				Computed: true,
			},
		},
	}

You can ref: https://github.com/microsoft/terraform-provider-azuredevops/blob/main/azuredevops/internal/service/build/data_build_definition.go