Loading Profile...
getting a cap error on after after_update
I made sure to turn on the api in the control panel.
triggering after callbacks for `deploy:update'
* executing `newrelic:notice_deployment'
* Getting log of changes for New Relic Deployment details
* executing "xxxxxxxxxxxxxxxxxxxxx"
servers: ["xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
[xxxxxxxxxxxxxxxxxxxxxx] executing command
command finished
* Uploading deployment to New Relic
triggering after callbacks for `deploy:update'
* executing `newrelic:notice_deployment'
* Getting log of changes for New Relic Deployment details
* executing "xxxxxxxxxxxxxxxxxxxxx"
servers: ["xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]
[xxxxxxxxxxxxxxxxxxxxxx] executing command
command finished
* Uploading deployment to New Relic
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
The best solution from the company
-
Coneybeare, the deployments feature is currently in early access. You are getting a forbidden response because your account is not enabled for early access features.
I’m sorry
The company and 1 other person say
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?coneybeare what am I missing? I don't see the error in the output you posted. Are you in the early access program? Can you follow-up to support@newrelic.com?
-
Inappropriate?** unable to notify New Relic of the deployment (Unexpected response from server: 403: Forbidden)... skipping
Sorry, looks like I didnt cut/paste the entire message -
Inappropriate?Coneybeare, the deployments feature is currently in early access. You are getting a forbidden response because your account is not enabled for early access features.
I’m sorry
The company and 1 other person say
this solves the problem
-
Inappropriate?Is this feature still in early access? I get the same error. What are the possible causes of this error? -
Inappropriate?No, it's a public feature now. Check support.newrelic.com for information on the feature. The likely cause of the error is that you don't have API access turned on in your account preferences. Login and go to the account page to check it.
EMPLOYEE
