Home → Questions →

Can we provide an ENCRYPTED password to the UI Environment variables which is used in the DEPLOY section?

• Edit

Pure Krome

25 Aug, 2017 03:48 AM

Problem: We're using UI Environment variables and one of them is our Azure Website password. If we encrypt this password and paste it into the UI, how do we use it in a DEPLOY section?

Details:

Currently, we have a number of AV projects which all reference the same appveyor.yml file. Each AV project has some environmental variables manually added to each project UI .. which of course is specific to each Project. Each AV project is a person's own branch testing.

Here is the yml..

  deploy:
    - provider: WebDeploy
      server: $(deployServer)
      website: $(deployWebsite)
      username: $(deployUsername)
      password: $(deploySecurePassword)
      remove_files: true
      app_offline: true

So if we go and manually encrypt this password at https://ci.appveyor.com/tools/encrypt how do we use it, in the above section?

1. 1 Posted by Ilya Finkelshte... on 25 Aug, 2017 10:03 AM

   

   If you manually encrypt this password at https://ci.appveyor.com/tools/encrypt, than you can simple use it this way

     password:
       secure: <encrypted_value>
   

   If you want to paste it to Environment UI, do not encrypt it before pasting, paste in clear text and press "lock" in UI to encrypt. Then us it as in YAML you provided.

   • Edit

2. 2 Posted by Pure Krome on 25 Aug, 2017 02:13 PM

   

   The problem we've found with the UI method is that you can easily UNLOCK it - just click that padlock and it's now visible.

   Just feels ... weird :( Would be kewl if we could provide the encrypted value and then somehow use it in the yml by specifying the secure: keyword.

   • Edit

3. 3 Posted by Ilya Finkelshte... on 28 Aug, 2017 08:26 AM

   

   We currently treat secure values as as string to decrypt, we do not try substitute them with environment variables. Please feel free to file issue for us on GitHub, will see what we can do.

   • Edit

4. Pure Krome closed this discussion on 20 Sep, 2017 07:16 AM.