feat: Add support for unix socket path and secure connection

[josecolella]

⚠️ Best reviewed commit-by-commit

This PR

• Add support for connection via unix socket path
• Add support for connection via secure connection

Related Issues

Resolves #5
Resolves #4

Notes

• Documentation for Channel Credentials
• Looking at the test, it seems that the secure connection can be constructed via with server roots certs only

Follow-up Tasks

How to test

@beeme1mr @toddbaert How would I test unix socket path locally. I'm using

docker run -p 8013:8013 ghcr.io/open-feature/flagd-testbed:latest

for flagd testing

[technicalpickles]

Since this is integrating with another service, I think it'd be extremely helpful/important to be able to validate that it is able to connect and interact with it.

You mention being able to locally with docker. I'd suggest making a docker-compose.yml to be able to bring that up. With that, you'd be able to add some RSpec hooks for making sure it's running. For example:

RSpec.configure do |config|
  next if config.dry_run

  config.when_first_matching_example_defined(type: :system) do
    # Run FlagD for integration specs
    unless config.dry_run
      # code to start flagd here
    end
  end

You'd need to either add :integration to the specs, or configure an RSpec to infer that based on a path, ie spec/integration. I'm not positive how that is done, as my initial searching seems to be tied to rspec-rails specifically.

[toddbaert]

Since this is integrating with another service, I think it'd be extremely helpful/important to be able to validate that it is able to connect and interact with it.

You mention being able to locally with docker. I'd suggest making a docker-compose.yml to be able to bring that up. With that, you'd be able to add some RSpec hooks for making sure it's running. For example:

RSpec.configure do |config|
  next if config.dry_run

  config.when_first_matching_example_defined(type: :system) do
    # Run FlagD for integration specs
    unless config.dry_run
      # code to start flagd here
    end
  end

You'd need to either add :integration to the specs, or configure an RSpec to infer that based on a path, ie spec/integration. I'm not positive how that is done, as my initial searching seems to be tied to rspec-rails specifically.

@technicalpickles One of the things we've done in the other SDK repos is implement this integration test suite, which relies on flagd (running in a container in CI), and this flagd provider to test basic SDK functionality.

Basically, it runs exactly what you propose, but to validate the SDK behavior end-to-end, including provider registration and the flag evaluation API. We could run the same integration suite here, or just a subset.

[josecolella]

@technicalpickles Was there anything else you saw for this PR that needed modification?

[toddbaert]

I see some changes around the config/ENV/default config merging, and I also see a (previously) skipped test here that might be impacted.

[toddbaert]

As we discussed in the CNCF slack, it seems like we can make the cert path optional, since Ruby will otherwise use system certs.

[technicalpickles]

Chatted with @josecolella, and the comments I've left can be followup improvements. So approving ✅