Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add OPA pooled HTTP client configuration parameters to CRD

Open
#956 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
kubernetes, rust

Research direction

Start by locating the NifiCluster CRD definition and the existing OPA authoriser configuration, then compare the available parameters with those introduced in pull request #31. Expose OPA_HTTP_POOL_SIZE, OPA_HTTP_CONNECT_TIMEOUT_MS, and OPA_HTTP_REQUEST_TIMEOUT_MS in the CRD, and verify that the generated schema and related configuration tests or checks accept them.

Written by the indexing model from the issue text.

Description

A recent pull request introduced changes to the OPA authoriser for NiFi so that the OAP client uses a pooled HTTP connection. There are new tuneable parameters introduced by this change that would made sense to expose in the NifiCluster CRD:

  • OPA_HTTP_POOL_SIZE
  • OPA_HTTP_CONNECT_TIMEOUT_MS
  • OPA_HTTP_REQUEST_TIMEOUT_MS
Dominant language
Rust
Stars
48
Forks
12
Avg merge
11h 26m
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/nifi-operator

All issues in stackabletech/nifi-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.