Home → Problems →

Strange behaviour with secure variables

• Edit

julian.elve

03 Dec, 2014 04:11 PM

A build script that used to work has started inserting the encrypted version of a secure variable. Bizarrely when we change the definition in the YML to be a standard variable, the encrypted version is still getting inserted. We're reasonably sure we are not referencing the wrong variable... Anyone else having a similar issue?

1. Support Staff 1 Posted by Feodor Fitsner on 03 Dec, 2014 04:32 PM

   

   Is it environment variable?

   -Feodor

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 03 Dec, 2014 04:33 PM

   

   Do you have this environment variable defined on UI, Environment tab?

   -Feodor

   • Edit

3. 3 Posted by julian.elve on 03 Dec, 2014 04:37 PM

   

   HI Feodor

   Yes it is, but I have not checked "ignore appveyor yml"

   Do you suggest I delete it from the UI?

   • Julian
   • Edit

4. 4 Posted by julian.elve on 03 Dec, 2014 04:45 PM

   

   Yes, environment.

   I have just tried deleting it in the UI and pushing another changeset with it in the yml as an unencrypted environment variable, and that is getting inserted correctly.

   I will now try again with it returned to secure

   • Edit

5. 5 Posted by julian.elve on 03 Dec, 2014 04:52 PM

   

   Yes, that now works with it marked as secure in YML

   Is this a designed behaviour, that UI overrides YML?

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 03 Dec, 2014 05:16 PM

   

   Yes, this is by design, but what worries me is that secure variable wasn't decrypted.

   I'm going to check this out.

   • Edit

7. julian.elve closed this discussion on 10 Jun, 2015 07:06 AM.