Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
My setup is the following:
Each node is a separate instance (e.g the deployer node is remote to the design node). I recently setup a govern node with which I track all bundles deployed on the automation node, as well as all APIs deployed to the api node. There is a setting that prevents you from deploying a bundle/api if it was not signed-off previously on the govern node. This setting is outlined here at the very top. I was able to use this setting as long as I used a local deployer, but once I switched over to a remote one, the setting disappeared. Is this intended behaviour or am I missing a particular configuration?
Thanks in advance,
Operating system used: Alma Linux
Hi @fsergot, thanks for your reply! 😃
I activated the govern node on both, the deployer and automation node (although I think on the deployer is sufficient). The governable items section on the govern node even gets populated with projects.
What I did so far:
That seems weird indeed. the display of the Dataiku Govern Policy is only driven by the activation of the govern integration on the Deployer node, nothing else (and even if the integration itself is not working, the dorp down is still available).
Which version are you using?
After almost 24h the dropdown appeared in the GUI of both, the automation node and the api node. This is odd 😐 Well, it apparently works now. Thanks for your time, I greatly appreciate it.