Skip to content
This repository was archived by the owner on Feb 16, 2023. It is now read-only.

Add custom error when secret is not found#239

Closed
Marton6 wants to merge 2 commits intodevelopfrom
feature/improve-secret-not-found-error
Closed

Add custom error when secret is not found#239
Marton6 wants to merge 2 commits intodevelopfrom
feature/improve-secret-not-found-error

Conversation

@Marton6
Copy link
Copy Markdown
Member

@Marton6 Marton6 commented Jan 16, 2020

No description provided.

@SimonBarendse SimonBarendse mentioned this pull request Jan 23, 2020
Copy link
Copy Markdown
Member

@SimonBarendse SimonBarendse left a comment

Choose a reason for hiding this comment

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

The path is really nice feedback to have when a secret cannot be found, so that you can better determine where the problem is.

detective gif

I think this is valuable for a lot more usecases, for example:

  • secrethub inject
  • (multiple) secrethub reads, e.g. in a script: ./my-script.sh
  • (multiple ) reads by the Terraform provider

Therefore, shall we add this in secrethub-go instead, so that every secret not found error includes the path in the error message?

@Marton6
Copy link
Copy Markdown
Member Author

Marton6 commented Feb 25, 2020

The path is really nice feedback to have when a secret cannot be found, so that you can better determine where the problem is.

detective gif

I think this is valuable for a lot more usecases, for example:

  • secrethub inject
  • (multiple) secrethub reads, e.g. in a script: ./my-script.sh
  • (multiple ) reads by the Terraform provider

Therefore, shall we add this in secrethub-go instead, so that every secret not found error includes the path in the error message?

Good point! I will implement it in the client.

@Marton6 Marton6 closed this Feb 25, 2020
@SimonBarendse SimonBarendse deleted the feature/improve-secret-not-found-error branch March 20, 2020 11:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants