Skip to content

Releases: Chaffelson/nipyapi

v0.21.0

08 Oct 13:43
3010452
Compare
Choose a tag to compare

What's Changed

  • Fix API model generator by @michaelarnauts in #356
  • issue-360: handle -9 error messages better by @ottobackwards in #361
  • Handle plain text response types so json values are correctly returned by @michaelarnauts in #358
  • update clients to 1.27.0 by @Chaffelson in #365
  • Simplified the use of setattr in recurse_flow, flatten, and list_all_by_kind methods in nipyapi/canvas.py.
  • Added support for key_password in the Configuration class and its usage in nipyapi/nifi/rest.py and nipyapi/registry/rest.py.
  • Fixed the method to retrieve HTTP headers in nipyapi/nifi/rest.py and nipyapi/registry/rest.py.
  • Updated pylintrc to match more modern python standards
  • Fixed issue #326 where the latest flow version was not being deployed by default
  • Fixes nipyapi.nifi.ProcessGroupsApi.upload_process_group_with_http_info() incomplete #310
  • VersionedReportingTask added with appropriate functions
  • Move docker requirement to extras to avoid dependency install during standard usage
  • Set latest python3 version to 3.12
  • Added NiFi-2.0.0-M4 to testing suite, appears to work but compatibility not guaranteed using currently 1.x clients
  • Deprecate usage of py.test in favour of newer pytest.
  • Update readme

New Contributors

Full Changelog: v0.20.0...v0.21.0

Update to NiFI 1.23.2

15 Apr 09:50
1d52262
Compare
Choose a tag to compare

What's Changed

  • NiFi 1.23.2 update by @Hexoplon in #330

  • Update Python support to 3.7 through 3.11.

  • Update get_access_policy_for_resource no policy test by @jrittenh in #317

  • Update README with NiFi 1.17 support by @rsaggino in #314

  • feat(config): add ReportingTaskEntity to registered filters by @Hexoplon in #337

  • remove library setting root logger configuration by @ottobackwards in #340

  • Fix ruamel.yaml pinning. Fixes docs and test process for EC2. by @Chaffelson in #346

New Contributors

Full Changelog: v0.19.1...v0.20.0

Update to NiFi 1.17

08 Aug 22:07
v0.19.1
33daf40
Compare
Choose a tag to compare

What's Changed since 0.17

  • New github release notes feature, woop
  • NiFi 1.17 support
  • Added link to doc index for parameter contexts by @Jimvin in #302
  • Allow version validation to ignore NiFi or Registry when checking for parameter support by @ChrisSamo632 in #304
  • Adds child cascading to assign_context_to_process_group by @sdairs in #267
  • Fix bug in security.bootstrap_security_policies by @PieterDM in #261

New Contributors since 0.17

Update to NiFi-1.16

13 May 20:12
v0.19.0
27b2228
Compare
Choose a tag to compare
  • modify utils.check_version to accept a default version to check against, and remove nested error when version check fails as it is overzealous
  • Update test file paths in test_utils in case someone runs tests as root which actually can write to fake devices and therefore break the tests
  • Updated clients for 1.16
  • Added pylint exclusions for known but unimportant complaints
  • Added workaround for NiFi 9470 by providing default inherited_parameter_contexts per advice from Chris Sampson in NiPyAPI Issue #305
  • Fixes #305
  • Updated NiFi and Registry versions in Docker compose configs to use latest 1.16.1 builds

NiFi and NiFi-Registry 1.15.0 support

29 Nov 17:53
v0.18.0
0d82220
Compare
Choose a tag to compare
  • Moved testing to secured single user by default for NiFi
  • Consolidated clients to the 1.15.0 release version for both NiFi and Registry
  • Updated logic to support changed working modes in tests
  • Corrected minor functional issues for 1.15 in login handling, SSL certs, Parameter Updates and Testing
  • Backwards compatibility and Regression tested as requiring no breaking changes

Python 3.9 testing and gzip headers

21 Oct 09:10
v0.17.1
fb67492
Compare
Choose a tag to compare

Added gzip as default request header (PR from @rsaggino )
Update ruamel.yaml to 0.17.16
Update file read/write to explicitly handle encoding per best practices; default to UTF8; configurable in nipyapi.config
Linting and style changes to update to Python 3.9 standards, except where it would break backwards compatibility to Python 2.7
Test support for Amazon Linux 2, mostly better error handling for filesystem responses

Update NiFi to 1.13.2 and NiFi-Registry to 0.8.0

13 Oct 08:40
v0.17.0
2a7f181
Compare
Choose a tag to compare

Update NiFi and client to 1.13.2
Update Registry and client to 0.8.0
Minor spelling and linting fixes
Removed travisCI build indicator as TravisCI itself has been broken for a while, will move to new build service
Removed extraneous nifidev and registrydev containers from tox-full docker-compose definition

Note that Python 3.9 has SSL issues, but the library is testing as normal with 3.5-3.8/2.7.

Minor fixes for NiFi 12.x matching release

11 Oct 13:33
v0.16.3
7c10f1a
Compare
Choose a tag to compare
  • Bump version: 0.16.2 → 0.16.3
  • Removed force reset of configuration.password and configuration.username to empty string. This was not increasing security, and was causing unexpected errors for users connecting to multiple services in a single script.
  • Add greedy control to versioning.get_registry_bucket and versioning.get_flow_in_bucket to avoid undesirable partial string match.
  • Update readme to reflect switch from 'master' branch naming to 'main'.
  • Update tox to pin testing to Python 3.8, as Python 3.9 is producing unexpected and unrelated SSL failures
  • Minor lint formatting improvements
  • Update docs for 0.16.3 patch release
  • Correct wording in Parameter Contexts warning when version support is unknown. It may drop the details, but it might also keep them.

Fix authentication and security CVEs on deps

10 Feb 17:42
v0.16.2
292aa1e
Compare
Choose a tag to compare

NOTE: If you are using secured Registry, this release will enforce access controls for the swagger interface which is used to determine which version of Registry is connected in order to correctly provide features - you may have to update your authorizations

  • Update requirements.txt to unpin future and lxml
  • Update lxml to 4.6.2 or newer to resolve vulnerability
  • Pin watchdog to <1.0.0 per their docs to maintain Python2.7 compatibility
  • Revert 0.14.3 changes to Authentication handling which introduced basicAuth support but resulted in some NiFi connections appearing incorrectly as Anonymous
  • Added simpler basicAuth control to force it via a config switch without changing tokenAuth and other Authorization header behavior during normal usage
  • nipyapi.config.global_force_basic_auth is now available for use for this purpose
  • Secured Registry users will now require the authorization policy to retrieve the swagger so we may use it to validate which version of
    Registry is in use for feature enablement
  • Moved all Security controls in config.py to a common area at the foot of the file
  • Removed auth_type from security.service_login as it is now redundant
  • Added controls to handle certificate checking behavior which has become more strict in recently versions of Python3, ssl_verify and check_hostname are now handled
  • security.set_service_auth_token now has an explicit flag for ssl host checking as well
  • Fix oversight where improved model serialisation logic was not correctly applied to Registry
  • Removed unusused parameter refresh from parameters.update_parameter_context
  • Reduced unecessary complexity in utils.dump with no change in functionality
  • Updated client gen mustache templates to reflect refactored security and api client code
  • Minor linting and docstring and codestyle improvements
  • Set pyUp to ignore Watchdog as it must stay between versions to statisfy py2 and py3 compatibility
  • If Client is not instantiated, optimistically instantiate for version checking
  • add socks proxy support

Fix Versioning with Parameters

11 Dec 10:35
Compare
Choose a tag to compare

Fix issue #229 where Parameter Contexts were not being correctly handled in Versioning with NiFi Registry.
Also add user warnings and version tests for when interaction between Registry and NiFi may lose data in older versions of each where Parameters are not supported.