Giter Club home page Giter Club logo

Comments (8)

sivaprf avatar sivaprf commented on July 18, 2024 2

I get the following error when i run the following command: Any idea why?
hal config provider appengine account add my-appengine-account --project $GCP-PROJECT-ID

  • Get current deployment
    Success
  • Add the my-appengine-account account
    Failure
    Problems in default.provider.appengine.my-appengine-account:
    ! ERROR Failed to connect to appengine Admin API: 403 Forbidden
    {
    "code" : 403,
    "errors" : [ {
    "domain" : "global",
    "message" : "Operation not allowed",
    "reason" : "forbidden"
    } ],
    "message" : "Operation not allowed",
    "status" : "PERMISSION_DENIED"
    }.

  • Failed to add account my-appengine-account for provider
    appengine.

from spinnaker.github.io.

danielpeach avatar danielpeach commented on July 18, 2024

Thanks - I'll update the docs.

With respect to the webhook, it looks like Github added a second source range for the webhook since I wrote the codelab (192.30.252.0/22 and 185.199.108.0/22, listed here). Try adding both to your firewall rule.

The codelab assumes you're running Halyard on a GCE VM - I would double check that your VM and firewall rule were set up according to the codelab.

from spinnaker.github.io.

madisona avatar madisona commented on July 18, 2024

Hi @danielpeach - thanks for the follow up. I saw that an added the other range and the webhook still doesn't work.

In fact, I carefully started the tutorial all over again with a brand new GCP project, carefully following each step and am still having the same issue. Here is what my configuration looks like for the VM, Firewall rules, and Github Webhook.

VM Settings
screen shot 2017-06-15 at 8 56 30 am

Firewall Rule
screen shot 2017-06-15 at 8 57 57 am

Github Webhook
screen shot 2017-06-15 at 8 52 24 am

I still get the message from github We couldn’t deliver this payload: Couldn't connect to server

from spinnaker.github.io.

danielpeach avatar danielpeach commented on July 18, 2024

I was able to reproduce this.

Run the following:

echo "host: 0.0.0.0" | tee ~/.hal/default/service-settings/echo.yml
sudo hal deploy apply

from spinnaker.github.io.

madisona avatar madisona commented on July 18, 2024

@danielpeach oh nice, thank you.. now the webhook is working!

before I ran the command I opened the echo.yml file and it appeared to already have that host: 0.0.0.0 in it. I ran your commands anyways and now things are good.

If you're looking to clean up a few other parts of the tutorial, here are just a couple other very minor things I noticed.

  • The New Application screen looks slightly different than the current screen shot (you don't set an account yet on the first page.
  • At the Pipeline Creation step, the tooltip isn't New, it is now Create Pipeline or Strategy
  • At the Webhook Trigger section, to be consistent with other areas, step 1 should be to click Add Trigger

Thanks again for this fantastic codelab!

from spinnaker.github.io.

danielpeach avatar danielpeach commented on July 18, 2024

Great, thanks - I've updated the codelab so that it works properly now.

The screenshots will have to be updated periodically as the UI drifts - I'll be sure to include your suggestions.

from spinnaker.github.io.

danielpeach avatar danielpeach commented on July 18, 2024

The command you've provided will work only if the application default credentials for the machine that's running Halyard have access to the App Engine Admin API.

I would verify the following:

  • That Halyard is running on a machine with application default credentials (e.g., on a GCE VM).
  • That those application default credentials have access to the App Engine Admin API.

If you're still seeing a problem, could you please open a new issue? This seems unrelated to the original issue here.

Thanks.

from spinnaker.github.io.

timini avatar timini commented on July 18, 2024

Hi I have spinnaker deployed on GCE using the instructions here
https://github.com/GoogleCloudPlatform/spinnaker-deploymentmanager

I have found the account for the compute instance hosting spinnaker and have added the App Engine Admin API role on to that account on the IAMs page.

I am still receiving the 403 error

from spinnaker.github.io.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.