[x] If you changed the values of the properties name, publisher, and galleryFlags in the vss-extension.json file, you have reverted them.
[x] If you changed the values of the properties id, name, author, you have reverted them.
[x] I have reverted any changes to the version number components in both vss-extension.json and task.json, OR I didn't change them.
I believe this should fix the issues #44, #48 and potentially #50 as well. The 3 issues are related to this task executing the pulumi login command in a shell without the process.env vars mapped to the executing shell. This prevented users from being able to use an Azure Storage backend when they would set additional env vars such as the AZURE_STORAGE_ACCOUNT and the AZURE_STORAGE_KEY env vars in the Pulumi step.
The other issue was that when using an Azure Service Connection, this task was only setting the ARM_* env vars, but not AZURE_* as required by the Azure SDK for Go, which is used by Pulumi for supporting Azure KeyVault as a secrets provider.
name,publisher, andgalleryFlagsin thevss-extension.jsonfile, you have reverted them.id,name,author, you have reverted them.vss-extension.jsonandtask.json, OR I didn't change them.I believe this should fix the issues #44, #48 and potentially #50 as well. The 3 issues are related to this task executing the
pulumi logincommand in a shell without theprocess.envvars mapped to the executing shell. This prevented users from being able to use an Azure Storage backend when they would set additional env vars such as theAZURE_STORAGE_ACCOUNTand theAZURE_STORAGE_KEYenv vars in the Pulumi step.The other issue was that when using an Azure Service Connection, this task was only setting the
ARM_*env vars, but notAZURE_*as required by the Azure SDK for Go, which is used by Pulumi for supporting Azure KeyVault as a secrets provider.