Ingo S.

Can you elaborate on what the issues are? It sounds like as if you have multiple people pushing to the same GitHub branch and the work they do conflicts with each other. Could that be the case?

Hi Paul, are you using GitHub.com, or an on-premises GitHub Enterprise installation? To better assist, it would be helpful to understand your environment in more detail, as well as the specific issues you’re encountering.

I do not think there is a way to do this with the CSV Formatter, If you specify the 7 Header Fields in the settings it will not write the raining 3 fields into the CSV, otherwise it will write out all fields with headers. My gut feeling says that you might need to convert all your fields into one string in a mapper via $.keys().join(",") and $.values().join(",") and then write that out with a Fixed With Formatter.

not every account setting allows you to use expressions, many only accept hardcoded values. If they allow expressions you can use an expression library and then refer to it in your pipeline and use it in the account but this is a hit or miss and will not work in all cases. If you intend to use different configurations/accounts in different environments you should create the accounts in each environments with the values that apply to this environment and then reference the name of the account in the snaps that need it. You can do something like this environment.expr file.

{
// Accounts, one in each environment.
    "SFTP_ACCOUNT": {
        "IT": "../../shared/SFTP Dev Account",
        "TEST": "../../shared/SFTP Test Account",
        "Prod": "../../shared/SFTP Prod Account"
    },
// Functions    
    getOrgName : () => pipe.projectPath.split('/')[1],
    getEnv : () => this.getOrgName().substr(9),
    getEnvValue : (key) => this.get(key).get(this.getEnv())
}

upload this as environment.expr to your shared folder and then reference it in the pipeline with the name env, Once you have that you can use lib.env.getEnvValue('SFTP_ACCOUNT') in the account of the Snap. You will however need to manage the hostname in each account.

Just to verify, you generates a RSA-SHA2 and pasted it into the SSH-Auth including the header and footer, correct? What is the error message you are getting when you try to connect.

I assume you gave the permission to use the role to the machine that runs the GroundPlex. Unless you do that there is no trust established between the GroundPlex and SageMaker. Do you have a chance to test on the OS level of the GroundPlex via the aws cli aws sts assume-role? The Snaps inherit this permission from the GroundPlex machine the pipeline runs on.

I have a customer that uses OpenSSH keys with the File Writer Snap. I unfortunately do not have a Windows/Putty environment but my understanding is that you need to export the key from the PPK in Putty. I see on the web that Putty Key Generator has a Conversion menu with a Export OpenSSH key option