This utility is planned to be archived later this year. The features provided by it are 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.
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.
I use ssh key to get access to my GitLab repository and not a username and password. When I use the versioning-client I get an Auth fail when try to push contents to my repository.
Details of error: org.eclipse.jgit.api.errors.TransportException: git@gitlab.my-git-details.git: Auth fail
I have gotten this to work on Linux, but not Windows. Most of our users are on Windows so this is an issue. Has anybody else experienced this?
I am having a similar issue to what sneham0002 said. The only difference is I'm exporting an excel file instead of the DDL files in the patch.
Has anyone found a solution to this?
While trying the buildSingleApp action does it consider packaging the DDL file in the package?
I am unable to deploy the application using the deployment Automation web UI, as the package generated by AVM is not containing the ddl files to execute, but the metadata property file refers to ddl file and the deployment fails because of the same.
nidhia - I suggest posting in community.appian.com/.../ as you'll get more visibility there.