Question regarding Imported Deployables

[jstarbird_7831]

Before I go and script this out using the API I wanted to check if there was a way to already do this.
I need to use deployables from two different applications so I have imported them into this new app.
What I am wondering about is that one of the imported ones has Config files that need to be deployed as well, can I just call Deploy Config from this new app and get that deployables configs or do I need to script that out using the API?

Product: BuildMaster
Version: 5.6.11

[ben]

Hello Jon,

Config files are not accessible via imported deployables, but artifacts are, so you can create an artifact in the source application and then do something like this:

Deploy-Artifact ArtifactName
(
    To: $WorkingDirectory,
    Application: $ReferencedApplicationName(DeployableName),
    Release: $ReferencedReleaseNumber(DeployableName),
    Package: $ReferencedPackageNumber(DeployableName),
    Deployable: DeployableName
);

[jstarbird_7831]

Follow up question, would the file that is in the artifact already have had the key pairs replaced when the artifact was made? And do I need to deploy the config file first and then make the artifact or will it just automatically be part of it?

What I'm needing to accomplish is deploy it using the same way if possible without having to replicate storage of the config in different apps. So replacing the key pairs under the new app if possible.

I know it would make more sense to make it part of the original apps but I cannot here because this is strictly on-demand deployments and we want to keep the restrictions on the pipelines requiring deployment to stages in order for the real apps.