Hi all, We've deployed a HDP 2.3 cluster with Ambari 2.2 using the Blueprints feature, which has worked out great for us. We have a bit of a complicated internal structure, but the key thing is that another department manages the infrastructure, and we provide the standard operating procedures.
*So:* is there any way to declaratively describe the state we want the cluster to be in *after* it's already been deployed? I'm aware we could use the Ambari REST APIs, and provide some kind of script to execute those as needed, but I wondered if there was a "better" way. We're not planning on moving the service hosts around right now, so I'm also wondering if destroying and re-deploying a new Blueprint is a good/OK/bad/terrible idea - I believe it doesn't stop the services when I destroy the cluster, so that might be a simpler approach. Does anybody have any idea if there's a simple "built-in" way to do this, or is it pretty much up to us to define how to apply changes to an existing cluster? Any insight appreciated, *Craig Roberts*
