build(deps): Update nipyapi requirement from >=1.5.1 to >=1.7.0 in /flows

[dependabot]

Updates the requirements on nipyapi to permit the latest version.

Changelog

Sourced from nipyapi's changelog.

1.7.0 (2026-07-18)

| NiFi 2.10.0 support and Azure DevOps Flow Registry Client integration

Supported Versions

• Bumped the supported and tested NiFi/Registry version from 2.7.2 to 2.10.0 and regenerated the NiFi and Registry API clients against the 2.10.0 OpenAPI specification. New Connectors API operations introduced operationId collisions in the generated clients; the affected hand-written call sites were updated accordingly (for example get_flow1, create_asset1, get_assets1, and the renumbered update_run_status variants).

Registry Client

• ensure_azuredevops_registry(): New nipyapi.versioning function to create or update an Azure DevOps Flow Registry Client. Unlike GitHub and GitLab (which use a personal access token), Azure DevOps authenticates with a service principal via OAuth2 client credentials, so the client is provisioned with the supporting management controller services.

Canvas Module

• create_management_controller() / ensure_management_controller(): New functions for controller-level (management) Controller Services — the kind referenced by Flow Registry Clients, which live at the Controller Settings level rather than inside a Process Group. ensure_management_controller is idempotent by name and validates supplied properties against the service's property descriptors.

CI Module

• ensure_registry(): Now accepts provider=azuredevops in addition to github and gitlab. Azure DevOps organization, project, repository, and service-principal credentials are read from arguments or the corresponding NIFI_ADO_* environment variables.

CLI

• Azure Pipelines output: The CLI now auto-detects Azure Pipelines (via the TF_BUILD environment variable) and emits ##vso[task.setvariable] logging commands so operation results round-trip as pipeline output variables. Can be forced with NIFI_OUTPUT_FORMAT=azurepipelines.

Documentation

• Added Azure DevOps / Azure Pipelines coverage to the CI operations guide (docs/ci.rst), the CLI output-format reference (docs/cli.rst), and the project README. See the companion nipyapi-actions repository for a complete Azure Pipelines example.

1.6.0 (2026-06-21)

| Port status visibility and consistent component recursion for CI functions

Bug Fixes

• get_status(): Processor counts (running_processors, invalid_processors, etc.) are now derived from actual processor enumeration rather than the Process Group's aggregate component counts. Previously these counts included all component types (ports, etc.), so invalid output ports were mis-reported as invalid processors.
• verify_config(): Controller service verification now recurses into descendant Process Groups (descendants=True), consistent with processor and port verification. Ancestor-inherited services remain excluded. Previously controllers in child PGs were not verified, so a broken controller in a sub-flow could pass CI.

CI Module

• get_status(): Now reports input and output port counts: total_input_ports, running_input_ports, stopped_input_ports, invalid_input_ports and the equivalent _output_ports fields. Invalid ports (e.g. an output port with no outgoing connection) are a real operational problem that was previously invisible to status checks. These are additive fields; existing output is unchanged.
• verify_config(): New verify_ports parameter (default True) adds input/output port validation. Ports with validation errors now appear in a new port_results key and cause verification to fail.

Canvas Module

• list_invalid_ports(): New function, parallel to list_invalid_processors, returning input/output ports with validation errors across a Process Group and its descendants.

Documentation

... (truncated)

Commits

• 759aae8 feat: add Azure DevOps Flow Registry Client support (#412) (#413)
• ea7070c chore: bump test NiFi to 2.10.0 and regenerate API clients (#411)
• e2785cd Surface controller services left disabled by schedule_all_controllers (#410)
• ba54425 Merge pull request #409 from Chaffelson/feature/ci-port-status-visibility
• 7bedd53 feat(ci): add port status visibility and consistent component recursion
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)