Eirik Lygre

My feedback

  1. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Azure Active Directory » Authentication  ·  Flag idea as inappropriate…  ·  Admin →

    This current behavior is as described, due to the refresh token issuance behavior of the v1.0 endpoint. However, we’re planning to fix this to require the developer to request `offline_access` within the next 3 months. Keep an eye on our release notes and this Uservoice entry for when this is fixed.

    In the interim, we’re changing the text of the offline_access scope to be more accurate and less alarming.

    Eirik Lygre supported this idea  · 
  2. 46 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Lab Services  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback! As more further investigate, the DevTest Labs supports VSTS Git and GitHub today. I’ve added this into the backlog. Given different Git repo offers different client for Labs to use and connect to, it’d be helpful if you could share with us which one you want to support first, so that the Labs can support them one by one. Thanks!

    An error occurred while saving the comment
    Eirik Lygre commented  · 

    Is there any progress on this?

    Eirik Lygre supported this idea  · 
    An error occurred while saving the comment
    Eirik Lygre commented  · 

    I would like to reiterate that the question of "which server" is wrong, imho.

    In this scenario, azure is simply a client needing to clone and pull a git repository. The same way that you use the same git client for any git server, azure should use a generic git client to clone/pull any server.

    The azure implementation then needs a url to the remote git repo, and either a ssh-key (for a ssh-based url), or http-credentials (for an http-based url).

    This will work with any repository, including github.

    Easy to do, and obviously wanted.

    An error occurred while saving the comment
    Eirik Lygre commented  · 

    In a sense, the question of which git repo to support is probably a wrong question :-). In principle, the DevTest Labs service should support the two main git-protocols (https and ssh), which together should support most repositories (GitHub, GitLab, Bitbucket, gogs, etc):

    The ssh protocol has fairly universal support, using the concept of a "deployment key" (supported by GitHub, GitLab, Bitbucket and probably most others). To use this, the user would create a custom ssh-key, upload the public part to the git repository and the private part to DevTest Labs. DevTest Labs would then use this key for its git-operations, and the repo would provide access as appropriate.

    The https protocol also has universal support, but only GitHub has an appropriate "deployment key" mechanism (they call it "personal access token"; for other repository managers you would have to provide your own username+password, which you really don't want).

    Hence, two steps forward:

    * First, support "any ssh-based git url" using a provided ssh private key ("deployment key")
    * Next, support "any https-based git url" using a provided https-authentication ("personal access token"), and wait for the repository managers to support this

    Solving only the first of these will enable all repositories. Solving the second will remove the need for a GitHub-specific solution.

    An error occurred while saving the comment
    Eirik Lygre commented  · 

    GitLab would be the absolute preference. They have a public GitLab.com-offering (running in Azure, no less), but they also offer the software for on-prem installation. The on-premise and cloud based software is the same, and DevTest Labs should support both.

    My preference would be for a ssh-based git-connection, as this allows the use of project specific deploy keys (instead of user specific keys, which give access to all repositories of a user).

    An error occurred while saving the comment
    Eirik Lygre commented  · 

    The "Add Artifact Repository" blade on the Azure portal does not allow me to enter anything other than a GitHub or Visual Studio Online repository, as shown on http://imgur.com/vdNt5T8.

    (The error message reads "Please enter a valid Git HTTPS clone URL from GitHub or Visual Studio Online. For example ...")

  3. 998 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →

    Hey Folks,

    We have made some great progress on this idea and most of our services today do support move resources across groups.

    We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.

    Please file individual asks on each service category present in uservoice and vote for it.

    Thanks,
    Azure Portal Team

    Eirik Lygre supported this idea  · 

Feedback and Knowledge Base