Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the error handling to include the status code and error details #13

Merged
merged 2 commits into from
Jan 8, 2018

Conversation

kgilpin
Copy link
Contributor

@kgilpin kgilpin commented Jan 4, 2018

What does this pull request do?

Conjur v5 provides error message details as JSON. Propagate these details when an exception occurs. Also, pass through the HTTP status code as an integer rather than a string embedded in the error message.

Also, in Conjur v5 the id argument can be fully-qualified: account:kind:id. Update the API to permit fully qualified ids.

Link to build in Jenkins (if appropriate)

https://jenkins.conjur.net/job/cyberark--conjur-api-go/job/feature%252Ferrors/

Questions:

Does this have automated Cucumber tests?

Yes

Can we make a blog post, video, or animated GIF out of this?

No

Is this explained in documentation?

The behavior of the Go client now better follows the REST API, by allowing fully-qualified ids and by returning the full error JSON.

Does the knowledge base need an update?

@ghost ghost assigned kgilpin Jan 4, 2018
@dustinmm80 dustinmm80 self-requested a review January 5, 2018 15:50
Copy link
Contributor

@dustinmm80 dustinmm80 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code changes look good to me. Tests are passing.

I think we should start keeping a CHANGELOG for this library and versioning it. We can do this with a CHANGELOG.md file and git tags. This will make it easier for downstream tools to pull in specific versions, like the rest of our API clients.

Can you add a CHANGELOG file? It can start with v0.1.0 (pre-merge) and the result of this PR merge can be v0.1.1 or v0.2.0 - whatever you prefer.

@kgilpin
Copy link
Contributor Author

kgilpin commented Jan 8, 2018

Ok will do

@dustinmm80 dustinmm80 merged commit 3936e4e into master Jan 8, 2018
@dustinmm80 dustinmm80 deleted the feature/errors branch January 8, 2018 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants