Expose Endpoint and Insecure on googlecloudpubsub exporter

[marcosrmendezthd]

Component(s)

No response

Is your feature request related to a problem? Please describe.

We are creating self-contained integration tests. While the pubsub receiver allows the endpoint and insecure configurations, the exporter does not.

Describe the solution you'd like

The ability to set the endpoint and insecure configuration options.

exporters:
  googlecloudpubsub:
    project: abc
    endpoint: mytestendpoint
    user_agent: projects/abc/topics/requests
    insecure: true

Describe alternatives you've considered

No response

Additional context

No response

[crobert-1]

Is this needed outside of testing environments? If it's only for testing there are existing internal options for endpoint and insecure.

endpoint and insecure definition in config:

opentelemetry-collector-contrib/exporter/googlecloudpubsubexporter/config.go

Lines 25 to 28 in 0a79aa8

	// Override of the Pubsub endpoint, for testing only
	endpoint string
	// Only has effect if Endpoint is not ""
	insecure bool

Example usage in a test:

opentelemetry-collector-contrib/exporter/googlecloudpubsubexporter/exporter_test.go

Lines 34 to 36 in 0a79aa8

	exporterConfig.endpoint = srv.Addr
	exporterConfig.UserAgent = "test-user-agent"
	exporterConfig.insecure = true

Is this what you're looking for, or am I missing something?

[github-actions]

Pinging code owners for exporter/googlecloudpubsub: @alexvanboxel. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[marcosrmendezthd]

yes @crobert-1 . that's exactly what I need. I'm making them public with some sed magic on my pipelines so that I can use a pubsub emulator and test what I need. I may send a simple PR for that if nobody can address it.

[crobert-1]

yes @crobert-1 . that's exactly what I need. I'm making them public with some sed magic on my pipelines so that I can use a pubsub emulator and test what I need. I may send a simple PR for that if nobody can address it.

I'm not sure I understand the situation fully, do you need these member properties to be public? If the tests are being added to this repository and module, you'd have access to the private properties.

[alexvanboxel]

I will expose the insecure field in both the receiver and the exporter (aligned with the other gRPC configurations in the collector)