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.
It should be compatible. It looks like the version just needs to be updated in the information section.
Hello,
As the version 21.2 has been published recently, is the Deployment Automation Manager compatible with it ?Because in the information section on the right, it doesn't seem to...
Best regards,
Jean-Jacques
v2.5.11 uses a newer version of Flyway (v6.5.5). See the release notes here: https://community.appian.com/w/the-appian-playbook/198/deployment-automation#release-notes
I think the Flyway Community Edition only supports database versions that are less than five years old.
facing issue with Automated Import (v2.5.11) for database deployment :
Status: Failed. Current step: Inspecting Application. Error message: Flyway Enterprise Edition or Oracle upgrade required: Oracle 12.1 is no longer supported by Flyway Community Edition, but still supported by Flyway Enterprise Edition..
It's encrypted as per TLS when communicating with the environment, but I don't think it's encrypted in-place.
Is there a way to encrypt the password stored in the import-manager.properties? This violates are security compliance.
Couple of critical enhancements which are needed on these tools . If any one has any work around for the below, please feel free to share.
1. Token based authentication. Storing password and user ID in property file is not best solution in terms of security.
2. Multiple parallel deployments. At a time two deployments is not possible. This will a blocker when 7-8 team as going to deploy.
3. Getting the detail logs at the end of import. There is a manual step to log in to tempo to get the details log. If we are doing CICD, then why again a manual step. The tool should share detailed log.
Yes we were creating a new branch from the master. We had used -branch_name.
Were you checking out the branch outside of the tool? It should be able to switch branches if you use the "-branch_name" option.
I guess we have found what was wrong.
When a new branch is created from master the versioning configuration was getting copied which was referring to master branch. After changing the configuration in the new branch to refer the new branch, we have not seen this issue occurring.