You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the software template actions the cloneAzureRepo (and I'm assuming the subsequent actions relating to Azure repo) fails with: "No token provided for Azure Integration".
After checking this comes due to the new Backstage release version 1.18 and the deprecation of the token field for the Azure Devops Integration. The new structure is as follows:
But the backend logic as shown here still refers to the old structure and this brings misleading errors when in fact the authorisation should work.
I believe updating the integrationConfig variable to mirror the new structure should fix it.
The text was updated successfully, but these errors were encountered:
When using the software template actions the cloneAzureRepo (and I'm assuming the subsequent actions relating to Azure repo) fails with: "No token provided for Azure Integration".
After checking this comes due to the new Backstage release version 1.18 and the deprecation of the token field for the Azure Devops Integration. The new structure is as follows:
But the backend logic as shown here still refers to the old structure and this brings misleading errors when in fact the authorisation should work.
I believe updating the
integrationConfig
variable to mirror the new structure should fix it.The text was updated successfully, but these errors were encountered: