Copado vs. Red Hat Ansible Automation Platform

When we have a large organization and number of changes and deployments are more than we should go for Copado. As we know it is a paid managed package and the cost is high so for dealing with fewer deployments it is not preferable to buy. Copado is well suited for users who don't have much technical understanding. So those users can see the User interface select the changes that need to be deployed by selecting the metadata. From Git operation to deployment all is handled by Copado itself. Copado has reduced the efforts for creating the package.xml and direct deployments can be done within a few clicks. Another Major aspect is that it can be directly synced with Jira or Azzure board from where the user stories will be synced and actions can be performed accordingly. For small organization, Copado can be expensive and to set up and maintain we need a technical person to do so.

Incentivized

The thing I mentioned earlier where we're constantly dealing with federal regulations or new agents that they want us to install and deploy and just getting those out in a consistent manner in a canned installation via Playbook is ideal

Incentivized

• Metadata Deployments
• Data Deployments
• Salesforce CPQ deployments that require a lot of various Data
• Transferring deployments between teams.

Incentivized

• Makes it easy to create and share automation in one central hub.
• Ansible content collections give me the ability to reuse code, making it rapid to carry out complex IT processes.
• Event-driven automation allows me to reduce manual tasks: it is rapid to know which action to take and respond automatically by receiving events from external apps automatically.

• Back promotions are sometimes difficult and behave in a weird manner
• After the deployment to production next changes in the pull request shows all the changes from the previous release as well
• Cannot be used through mobile

Incentivized

• Workflows should have more flexible paths than just success or failure.
• The upgrade process can be challenging with differences in security and environment.
• There is an opportunity to add CICD functionality into the tool.
• For development, it would be nice to have the option of editing a repo directly from AAP to allow quick tests/reruns. Then, allow it to push the updates back or create a new branch/PR in GitHub.
• The RBAC is good but could use improvements. One example would be an option that allows admins to assume the access of another user to validate it works as expected.

Incentivized

We are deploying Ansible at all levels of the organization

Incentivized

the yaml is easy to write and most people can be taught to write basic playbooks in a few weeks

Incentivized

Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.

Incentivized

There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.

Incentivized

I spoke on this topic today!

Incentivized

Flosum is a downgrade for sure and I do not recommend it. Gearset is an upgrade and my preferred solution. Gearset has simplified the deployment path and makes it very easy to move between Salesforce instances. If there are any difficulties with Gearset they also have the best customer support for any deployment tool I've tried. Overall I'd say Gearset is #1, Copado #2 and Flosum a distant #3.

Incentivized

AAP doesn't truly stack up against any of the products mentioned except for Aria Automation. But, it is extensible and open and has a lower cost to entry.

Incentivized

• It has reduced the efforts to create package.xml manually and deploy the changes
• Another positive impact is that we can track the commits to which org they have reached in an organized way and we don't need to maintain them separately
• For setting Copado it take a lot of time and training is required for the complete setup which is time-consuming

Incentivized

• Red Hat Ansible Automation Platform offers automation and ML tools that allow me to automate complex IT tasks.
• Through automation analytics, it is seamless to gain full visibility into automation performance allowing me to make informed decisions.
• Red Hat Ansible Automation Platform allows me to move rapidly from insights to action.
• Creating and sharing automation content in one place unify a team in one place hence enhancing real-time collaboration.