The features provided by this utility are now available out of the box (OOTB) in Appian versions 23.2+. For more information, refer to the Deployment APIs documentation.
Overview
This utility automates the process of inspecting the application, executing DDL scripts, updating CDTs, republishing the appropriate datastores, and importing the application.
With the Automated Import Manager Client, users can automatically deploy applications and package contents (either applications from Appian OR packages generated from the Automated Versioning Manager) to any environment. This utility provides the scripts that support triggering deployments from an external CI tool or deploy from the command line.
Key Features & Functionality
Automated Import Manager:
For more information, please see visit: https://community.appian.com/w/the-appian-playbook/198/deployment-automation
Note: This utility does not support Java version 9.0.
while testing this with svn I faced an issue like this "org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Negotiate authentication failed: 'No valid credentials provided'
The only change we have made is to fix the bug in executing DDL scripts:July 2019 - Release 2.5.8
A couple questions.
1. What changes were made in the July update?
2. Is there an issue with the automation manager pushing code to GIT?
I use PortableGit to push Appian Applications to BitBucket. Last month I noticed that the automation manager unzips my application into the appropriate files locally and sends a commit message to Bitbucket but it no longer pushes the files. I thought it was because I was still on client version 2.5.7 but its still happening with version 2.5.8. My current work around is to manually add all changes and push it to my branch using git. Does anyone else experience this? How can I troubleshoot this as none of my configurations in version-manager.properties have changed?
Is there an example application and database configuration that might demonstrate how this is meant to work? I think that would go a long way to solve the problem.
I am having difficulty getting Flyway to work with the import. I created a community post (https://community.appian.com/discussions/f/administration/17152/flyway-implementation) and have an issue open with Appian Support (477952) with details and files. I believe now that the issue is with the version-manager configuration, as the zip file does not look quite right.
Through DAM application fails to deploy. Is there any way to publish data stores through the deployment automation as it deploys whole app.
HI Aneeshv,We currently don't support password encryption. We suggest to secret store software like Vault in your testing framework to store the password and provide it at runtime when running Deployment Automation Manager.
We need the password to be encrypted in the deploy-application.sh script. Can you please tell us the steps on how to do it? deploy-application.bat -application_path "PATH TO APPLICATION ZIP" -username SERVICE_ACCOUNT_USERNAME -password SERVICE
I have gotten around the auth error by using Putty instead of OpenSSH. Unfortunately I have a new problem. The version-application runs, but does not do anything and does not respond when I try kill it.
Hello brendonp, for GitLab you can create an access token to use in the password field in the properties file as opposed to your actual password. To do so, you can follow this link here: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html. For the repoUrl, make sure to use the https URL instead of ssh. This way, it will function the same as if you used ssh without jeopardizing your password. Please let us know if you have any additional questions.