Tag - vRealize SaltStack Config

While exploring vRealize Automation and SaltStack Config, I had the bright idea to expand the integrations across the vRealize Suite by automatically installing the vROPs Telegraf agent during a vRA Deployment. This would provide immediate guest OS monitoring and (optional) application monitoring to every machine deployed from vRA. What you’ll need: vRealize Automation 8.8 vRealize SaltStack Config 8.8 Integrated with vRealize Automation through either vRealize Suite Lifecycle Manager or as a standalone SaltStack instance.

I was trying to install the vRealize Operations Telegraf agent on my VMs by following the documentation. I wrote the steps out in a Salt state file: unzip: pkg.installed install-telegraf: cmd.script: - source: https://cloudproxy.domain.tld/downloads/salt/download.sh - name: /tmp/download.sh -o install -v vrops.domain.tld -u admin -p p@ssw0rd - mode: '0777' Salt takes the source and puts it in the location under name, executing it with the included arguments. However, everytime it ran I would get this:

During some recent lab work, I deployed a fresh vRealize SaltStack Config 8.8 appliance in my lab and had it integrated with vRA and vIDM. On first login I found that my vIDM/vRA administrator (config admin) was unable to see the minions in SaltStack Config UI. After some trial and error and working with some others internally, I found the issue was related to the default permissions provided by the vRA IAM integration.