Hi community, I'm just sharing some ideas here.
I. Parameter Context should be inheritable. II. In the settings of process groups, it would be great if you could see the values directly to the right of the first tab when selecting the parameter context. Space is more than enough. III. deleting queues is easy, but don't be annoyed that you can't just click on Delete Queue and the small popup window will be with ok lock beard. Why wait? I regularly open a new Nifi window, because waiting is too stupid for me. IV. As soon as the system grows and you release e.g. only teamwise certain parameter contexts. The user sees under parameter context all entries, only those ones, which the user is authorized for. The others are to be seen as ID. By default "Show only mine" as a small checkbox oven on the right would be a dream. V. I don't know if this is possible, but especially for transports from Nifi Dev to Nifi Test i would like to have the possibility to use another option commit changes directly to Nifi test without any Nifi client or. GitHub hook magic. VI. Bearer tokens can, to my knowledge, only be used as attributes in Invoke http. A really serious disadvantage is that I cannot define and use the key itself as a sensitive value in the parameter context. This contradicts my demand for transparency (make all pipelines visible across teams including configuration in the parameter context, by default the data view of the flow files is disabled for non-team members and all edit permissions are disabled). You would need a sensitive optional attribute bearer token in the invokehttp processor.
