I am having issues deploying an update to a current app which was last deployed in July 2019.
It asked me to enable Cloud Build.
I had to first enable billing account for the app. I did this. I then enabled the cloud build API.
I now get a permission denied error when I run gcloud app deploy. The docs say to check the service account permissions, but when I load that page it says I need to enable the Cloud Build API. I click on the link and it shows me that the API is enabled. I click manage, go settings, and it says "The Cloud Build API needs to be enabled before changing the permissions of the service account."
Usually enabling an API takes few minutes before you can use it. Can you try again deploying your app?
Additionally, you don't need to add any new permission to your cloud build service account unless you are using cloud build in some kind of CI/CD pipeline. in That case you need to add some few more permissions to this service account.
You can always check which APIs are enabled using gcloud command line.
I'd suggest try to disable and re-enable the API, wait for a few mins and try again.
UPDATE:
The issue described might be a result of a known issue.
I suggest you star this Public Issue to stay updated.
Related
We have a heroku review app pipeline configured with github integration.
Currently, every time after a new app is created, we have to go in and manually disable automatic deploys in the UI here:
I was looking around for one of the following options to remove this manual step:
call an api to disable auto-deploy on a review app
change a pipeline level setting that determines the default value of auto-deploy for new review apps that get created
but so far I haven't been able to find anything.
Any suggestions for how this might be achieved would be much appreciated.
I want to deploy a private GitHub repository with Cloud Run on Google Cloud Plattform.
In GitHub, I properly installed Google Cloud Build Application by clicking "Authenticate" in Cloud Run.
But somehow, Google tells me "Currently not authenticated" even though I clicked it another time.
In Cloud Build I checked and it tells me "Google Cloud Platform was not authorised to list repositories".
What am I doing wrong?
For other persons, I my case, I use mutiples account of google, and my account of GCP is a seccond, when i auth in github, the callback redirect to first account. For resolve, I log-out all account and log-in only in my gcp account.
:)
yesterday i installed Azure Devops 2019 (2020) and everything was ok.
i created my first collection
then i granded permission to my friend as collection administrator in its group
then we checked this button and grant permission to others via panel
But today security button hide for both of us (today my security button disappeared and gone )
You can try deleting and redeploying the Azure DevOps server to see if there is still the question.
By the way, you can use the REST API to view the security of the collection. This REST API was not documented, and I found it using the developer console (F12 in most browsers).
GET https://{instance}/{collection}/_settings/security?__rt=fps&__ver=2
When I try to update the environment variables on an Azure DevOps release pipeline, I get the error below.
GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub repository. GitHub returned the error 'Resource not accessible by integration'.
I am an admin on the GitHub repo.
In Get sources, it is currently configured for a GitHub OAuth Service Connection. Another user is able to update the environment variables. I am using GitHub (not enterprise).
Is this an Azure DevOps permission that I do not have?
Is this an Azure DevOps permission that I do not have?
This error message usually comes with GitHub App installation token service connection.
Go Project Settings => Service Connections to check the details of the specific service connection. If your service connection is GitHub App installation token based service connection, then it's expected behavior to meet that issue. Our team are working on adding that support so far, please check this ticket.
Workaround:
1.Create a new service connection with OAuth/PAT method and use it in your pipeline. Since you're admin of the github repo, a Github PAT is more recommended.
2.If you have permission to the service connections and to the pipeline, this issue won't occur. Ask your Azure Devops project admin to via manage security.
After working with ADO tech support, it was discovered that we needed to remove the artifact and trigger definition from the release pipeline, and then re-add it. It is believed that there was cached service connection, and this updated the pointer to the correct service connection.
I was facing a similar issue when attempting to enable CI for a build and found this article and after digging in deeper I discovered that the issue was the actual PAT we created for the automation. What we missed originally was enabling the admin:repo_hook for the repository. This took longer to uncover than it should have, but just wanted to add that, as removing and re-adding things didn't really do anything for us.
I'm developing an azure function in VS Code. I have the Azure Functions extension installed.
I have created the function and its running locally just fine.
But when I sign in to azure using the extension it does not see any of my Azure subscriptions. Therefore I can't select a subscription and deploy the function.
Has anyone else encountered this and found a workaround?
I had the same problem and I was able to sign in by clearing the azure tenant id in the azure extension settings for VS Code
You can try to the following ways to troubleshoot.
1.Go to azure portal and login your account to check if the account has active subscription listed.
2.In VS code, try to sign out and sign in again.
3.Use the below script with azure cli to login your account
az login --debug
4.If you have set MFA for your account, re-open the browser and re-login to the portal, which triggered the wizard for me to configure all needed for MFA authentication. After that, az login works again.
Move your mouse to there, you will see a filter icon.
Click it, then you will find all subscriptions.