I have a problem creating a new repository in Cloud Source Repository (console or gcloud).
In the gcloud case, when I run the following command using either an user account with roles/owner or a service account with roles/source.admin:
gcloud source repos create new-repo
I get the following error:
ERROR: (gcloud.source.repos.create) ResponseError:
status=[PERMISSION_DENIED], code=[403], message=[User [xxx#xxx] does
not have permission to access projects instance [PROJECT_ID] (or it
may not exist): The caller does not have permission].
The project currently has no repositories associated to it. I was able to create one earlier (through the console) which I then deleted before using. I have been unable to create any subsequent repositories since.
Would love to hear some suggestions if anyone else has faced a similar issue.
As you mentioned to have the proper roles on the account this issue is due to not having a billing account linked to the project.
The API methods used to create a repository require the billing on the project to be enabled so to solve it if this is the issue you can perform the following steps
Go to https://console.cloud.google.com/billing
Select the project where you want the repository to reside
Click on Link a Billing Account
A Popup message will show, over there click on Create Billing Account
Follow the wizard
Related
I'm running into an error code in the Pull request manager Hub in the Azure DevOps:
There was an error during the extension load: TFS.WebApi.Exception: TF401027: You need the Git 'GenericRead' permission to perform this action. Details: identity '...', scope 'repository'.
which leaves me a bit baffling since the team lead and manager is already sure that I have permission to view pull request, I could even comment and fix pull request that I was added on, but the manager hub is where it refused to show up for me.
the permission management
enter image description here
This error occurs when a user with a stakeholder license tries to create a repository
Solution: Upload the license of the user from “StakeHolder” to “Basic” or get him MSDN Visual Studio Professional or Enterprise subscription
By default stakeholders won’t have access to repos but they can try to create repository from organization settings..
We want only some people to be able to create 'release/*' branch in Azure DevOps cloud(?) repo.
Unfortunately, I couldn’t find this option in UI.
I also couldn’t find it here
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies?view=azure-devops
and here
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-permissions?view=azure-devops
I tried to implement it with REST API but my attempts were unsuccessful.
I also didn’t find any extension which could help me with this.
I'm still looking for a solution.
There is not option in the UI to set the create branch permission for branches.
However, you can achieve this by runing tf git permission commands in Developer Command Prompt for Visual Studio to deny the permission to create branches under releases. See below example:
Below command will block the users in Contributors group creating branches under releases
tf git permission /deny:CreateBranch /group:[MyProject]\Contributors /collection:https://dev.azure.com/MyOrganiza/ /teamproject:MyProject /repository:myRepo /branch:releases
Check Git Permission Command for more information.
I'm trying to deploy an ADF pipeline using CICD (Azure DevOps Deployment) using a release pipeline.
Here I'm trying to merge stuff from my Collaboration branch to master (usig GIT).
I'm also using:
Azure Deployment:
Create Or Update Resource Group action on SiteOpsConsolidatedProd (Agent Job) as a part of the Continuous Deployment Process
I'm getting the following error:
[error]At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.
[error]Details:
##[error]BadRequest: The document creation or update failed because of invalid reference 'irslinked'.
##[error]Check out the troubleshooting guide to see if your issue is addressed: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting
##[error]Task failed while creating or updating the template deployment.
irslinked is the name of a self-hosted IR (Linked)
this IR: irslinked is also included in the overwrite template parameters list.
As suggested by Microsoft in their ADF CICD best practices, the self-hosted IR should be hosted on a dedicated ADF instance and should be of type shared and linked to the dev/test/prod instances.
Link to the documentation: https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment#best-practices-for-cicd
Please respond if it works.
This may be helpful for someone. I had a similar invalid reference error. Actually, my ADF was imported from git. I have reconfigured the git with "import existing resource to repository" option.
Azure documentation https://learn.microsoft.com/en-us/azure/data-factory/ci-cd-github-troubleshoot-guide#recover-from-a-deleted-data-factory
If customer had a Self-hosted Integration Runtime in deleted ADF, they
will have to create a new instance in new ADF, also uninstall and
reinstall the instance on their On-prem machine/VM with the new key
obtained. After setup of IR is completed, customer will have to change
the Linked Service to point to new IR and test the connection or it
will fail with error invalid reference.
I had this error message but it referenced a resource that didn't even exist.
I was able to solve it using steps from here:
https://learn.microsoft.com/en-us/azure/data-factory/source-control#troubleshooting-git-integration
Notably:
Disconnect from existing git repo.
Reconnect back to the same repo, but select "import existing resources" into a "Create new git branch".
Then use git to create more commits on top of that branch, which remove all the extra crud that got generated, until the codebase is back to the desired state.
Note that I had to have sequential commits deleting stuff in dependency order, before it would work. i.e. Pipelines, then dataflows, then datasets, then linked services, then Int.Runtimes.
I only seem able to integrate my ADFv2 instance with public repos in my organisation, which is undesirable.
In the documentation (https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/data-factory/source-control.md#author-with-github-integration), it states that:
..can use both public and private GitHub repositories with Data Factory as long you have read and write permission to the repository..
So, i complete the following steps:
Navigate to my GitHub Org.
Create a new "Private" repo, initialised w/ README.MD.
Create a new "Internal" repo, initialised w/ README.MD. (this is GitHub Enterprise Cloud)
In the Azure Portal, create a new ADFv2 instance without Git integration.
Click "Set up code repository" in the ADFv2 instance.
Choose, RepoType: GitHub - Authenticate w. GitHub pop-up.
Enter org name in to the GitHub Account section.
Git repo name: No results found
🤷🏼♂️
The solution turned out to be the need to grant access as an Authorized OAuth App to the organisation. I did not have permission to do this.
You can then find it under 'Applications' once done.. but i think when you first connect up your ADF to GitHub, it prompts you if you would like to grant it.
I was not seeing this due to permissions on the Org.
I'm having an issue getting access to our private NuGet packages hosted on Azure DevOps for a new developer:
error : Unable to load the service index for source https://pkgs.dev.azure.com/company/_packaging/CompanyPackages/nuget/v3/index.json
I have generated a PAT from DevOps and modified the NuGet.config file. We have been using private NuGet feeds from DevOps for a year or two and I noticed Microsoft recently changed their billing model for Azure Artifacts so I'm wondering if this is part of the issue.
Do I need to opt in the new storage model for this new developer to be able to access the private NuGet feed or is there a way to attach a "Package Management" license to this new user?
This doesn't sound license-related. We've removed all license checks in Artifacts (so, no need to assign one to your new developer) and you're under the free tier limit of 2 GB (so, anyone in your organization with permissions to a feed should be able to access it).
Since it's a brand-new PAT, it shouldn't be expired (my first thought). But, some other things to try:
Check that the user for whom you generated a PAT has permissions to the feed they want to use
Ensure that the PAT you generated is either all-scopes or includes either the Package (Read) or Package (Read, Write) scopes