Automating NiFi flow deployments from DEV to PROD

แชร์
ฝัง
  • เผยแพร่เมื่อ 28 ก.ย. 2024
  • This video is a refresh of a webinar I did about 2 years ago on how to automate flow deployments across environments. Here is the previous video: • Demo Jam Live Returns:...
    This new video goes one step further and leverage the new concept of Parameter Context Providers in combination with the Scripted Hook in the NiFi Registry to nicely automate the deployment of a new version of a flow from a development cluster into a production cluster.
    Here the script shown in the video:
    gist.github.co...
    Some additional resources:
    bryanbende.com...
    bryanbende.com...
    bryanbende.com...
    Thanks for watching and feel free to leave a comment!

ความคิดเห็น • 7

  • @oyeyemirafiuowolabi2347
    @oyeyemirafiuowolabi2347 ปีที่แล้ว

    Thank you very much for this.

  • @santhoshsandySanthosh
    @santhoshsandySanthosh ปีที่แล้ว +1

    🤯 Super

  • @vincenzolombardo7722
    @vincenzolombardo7722 4 หลายเดือนก่อน

    Great video ! (I'll replace a lot of wait/notify processor)

  • @just__mjay
    @just__mjay 8 หลายเดือนก่อน

    Thanks for this. I loved it

  • @yogesh013
    @yogesh013 7 หลายเดือนก่อน

    This is awesome. Great Video.

  • @romanwesoowski6445
    @romanwesoowski6445 7 หลายเดือนก่อน

    Thanks for the great video
    What does that work with git flow provider instead of DB?

    • @pvillard31
      @pvillard31  7 หลายเดือนก่อน +1

      You can't have two NiFi registry instances pointing at the same git repo but if you have a single NiFi Registry across your different environments, then the same approach can be applied, yes.