You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Nimrod Avni (JIRA)" <ji...@apache.org> on 2019/02/01 09:53:00 UTC
[jira] [Updated] (NIFIREG-223) Flow version should have tags
[ https://issues.apache.org/jira/browse/NIFIREG-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nimrod Avni updated NIFIREG-223:
--------------------------------
Description:
Similar to git repositories, I think specific version of flows should have the ability to have tags, and have the options to add tags to already committed versions and to changes you are about to commit
I think this feature is very important in that it gives you more control to know which versions are ready for production and which ones are not (since we don't have the option of branches)
I think this feature should have a few features to come alongside it
* Every flow can be tagged with multiple tags
* Optionally, set a white list of tags you allow flows to be tagged with
* On a secure registry, have policies to add specific tags for specific users/user-groups (for example, if I am the NiFi admin, I don't want developers to decide which version is production ready, so have a policy where the "PROD" tag can only be added by admins)
* have the options to remove tags
This will be a great feature and will help to better manage flows and versioning
was:
Similar to git repositories, I think specific version of flows should have the ability to have tags, and have the options to add tags to already committed versions and to changes you are about to commit
I think this feature is very important in that it gives you more control to know what version are ready for production and which ones are not (since we don't have the option of branches)
I think this feature should have a few features to come alongside it
* Every flow can be tagged with multiple tags
* Optionally, set a white list of tags you allow flows to be tagged with
* On a secure registry, have policies to add specific tags for specific users/user-groups (for example, if I am the NiFi admin, I don't want developers to decide which version is production ready, so have a policy where the "PROD" tag can only be added by admins)
* have the options to remove tags
This will be a great feature and will help to better manage flows and versioning
> Flow version should have tags
> -----------------------------
>
> Key: NIFIREG-223
> URL: https://issues.apache.org/jira/browse/NIFIREG-223
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Nimrod Avni
> Priority: Major
> Labels: nifi-registry, tags, version
> Fix For: 0.4.0
>
>
> Similar to git repositories, I think specific version of flows should have the ability to have tags, and have the options to add tags to already committed versions and to changes you are about to commit
> I think this feature is very important in that it gives you more control to know which versions are ready for production and which ones are not (since we don't have the option of branches)
> I think this feature should have a few features to come alongside it
> * Every flow can be tagged with multiple tags
> * Optionally, set a white list of tags you allow flows to be tagged with
> * On a secure registry, have policies to add specific tags for specific users/user-groups (for example, if I am the NiFi admin, I don't want developers to decide which version is production ready, so have a policy where the "PROD" tag can only be added by admins)
> * have the options to remove tags
> This will be a great feature and will help to better manage flows and versioning
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)