Releases: plexsystems/nifi-cluster-coordinator
v0.0.3
v0.0.3-rc1
Bugs Fixed
- An issue where ID's for users and groups was not getting cleared out between clusters
New Feature
- You can now split your
yaml
configuration across multiple files and point a new flag--configfolder
at this folder. Thenifi-cluster-coordinator
will attempt to read allyaml
files in the directory and apply that configuration..
v0.0.2
v0.0.2-rc2
Squashed bug related to multiple clusters and parameter contexts.
Nothing to see here. Move along.
v0.0.2-rc1
v0.0.2-rc1
changes from v0.0.1-rc3
We overhauled how parameter contexts are assigned to process groups. You can now override an environment parameter context by setting the parameter_context_name
property on an environment.
component_access_policies
now can accept an optional clusters
array which will limit the scope of where these policies are applied. If no clusters
section is present the coordinator will attempt to apply the policy to all clusters. Leveraging this section will help to limit the number of warnings thrown if certain clusters only have a few process groups.
In this example there are 3 clusters foo
, bar
, & baz
. The coordinator will push the nifi flow
view the component policy to all three clusters. It will push the foo-project
view the component policy to the foo
and bar
clusters.
clusters:
- name: foo-cluster
- name: bar-cluster
- name: baz-cluster
<snip>
security:
component_access_policies:
- name: 'view the component'
component_type: 'nifi flow'
component_name: root
user_groups:
- cluster-admins
- everyone-users
- name: 'view the component'
component_type: 'project'
component_name: 'foo-project'
user_groups:
- foo-group
clusters:
- foo-cluster
- bar-cluster
v0.0.1-rc3
rc3
includes fixes for some bugs that were discovered related to the handling of parameter contexts
v0.0.1-rc2
Second release candidate of the nifi-cluster-coordinator
v0.0.1-rc1
Initial release candidate for a v0.0.1
release.
This is intended to be used to test functionality.