Concatenating input and string

[OskarKlintrot]

I can't find any examples for taking an input and using it in a magic command. I thought + would concat strings but this didn't work:

#!connect mssql --kernel-name mydatabase "Server=" + @input:Server + ".database.windows.net; Authentication=Active Directory Password; Database=" + @input:Database + "; User Id=" + @input:Username + "; Password=" + @password:Password" + ";"

Can I escape the input? Use a variable?

[jonsequitur]

This isn't directly supported. One approach that will work is to concatenate them into a single variable and then reference that in the magic command:

[jonsequitur]

A variation on that approach is to use #!set:

[OskarKlintrot]

Awesome! Thanks for both examples!

[OskarKlintrot]

Am I doing something wrong or did I run into a bug @jonsequitur?

This block:

#!set --name Server --value @input:Server
#!set --name Database --value @input:Database
#!set --name Username --value @input:Username
#!set --name Password --value @input:Password

var connectionString = $"Server={Server}.database.windows.net; Authentication=Active Directory Password; Database={Database}; User Id={@Username}; Password={@Password}; Encrypt=True;";

Sets the password everywhere:

[OskarKlintrot]

I just noticed that when using await Kernel.GetPasswordAsync("password"); the password can't actually be used to connect to the database... I'm guessing that it's sending * * * * * * * * to the server. I thought the @ maybe did something magical but it doesn't work with or without it. If I use GetInputAsync it works fine. All I want to do is not to version control my credentials 😅

[jonsequitur]

That's definitely a bug. I'm looking into it. It looks like the workaround is to put each #!set command into a different cell.

[muhahaaa]

That's definitely a bug. I'm looking into it. It looks like the workaround is to put each #!set command into a different cell.

We encountered the same problem when using GetPasswordAsync when creating a SQL connectionString. @jonsequitur Do you know if a fix for the bug is planned?

[jonsequitur]

The first bug described above is fixed:

[jonsequitur]

Kernel.GetPasswordAsync returns a PasswordString. This is meant purely for obfuscation. You can get the underlying value by calling PasswordString.GetClearTextPassword: