The Deployment Automation Manager consists of two tools used for:
Although the tools are best used in conjunction, they can be used independently as well.
The Automated Versioning Manager is a tool that helps manage Appian applications and database DDL files in a version control system. Given an Appian application ZIP file, the Automated Versioning Manager performs the following actions:
The goal of this tool is to facilitate the adoption and usage of a version control system to perform configuration management of the Appian applications and database DDL files.
With the Automated Import Manager, users can automatically deploy applications and patch contents (either applications from Appian OR packages generated from the Automated Versioning Manager) to any environment. Users will have three options for deployment: the tool can either deploy from the tool’s user interface in one click, trigger the deployment from an external CI tool or deploy from the command line.
The Automated Import Manager automates the process of inspecting the application, executing DDL scripts, updating CDTs, republishing the appropriate datastores, and importing the application.
For more information, please visit: https://community.appian.com/w/the-appian-playbook/198/deployment-automation
the solution was to override the order of the authentication methods by adding the following on the version-appliation.bat "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic" in case the svn has Basic authentication. Or we can use any of the other options like this "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM" it will depend on your needs
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.
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: firstname.lastname@example.org: 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.
© 2019 Appian. All rights reserved.