Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Azure Devops Integration properties to be compatible with version 1.18 of Backstage #17

Closed
germelindam opened this issue Sep 27, 2023 · 2 comments

Comments

@germelindam
Copy link

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:

integrations:
  azure:
    - host: dev.azure.com
      credentials:
      - organizations:
         - organizationName
        personalAccessToken: ${PAT}

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.

@antoniobergas
Copy link

Hi, I'm trying to deal with the issue, for now I just downgrade to version 1.17.5.

This will give you some extra info about the current state:
Parfuemerie-Douglas/scaffolder-backend-module-azure-pipelines#30

https://discord.com/channels/687207715902193673/1154845617756065932

@antoniobergas
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants