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.

Sign up for GitHub

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

Jump to bottom

Remove AWS Provider verbiage from error messaging #24

Closed
bflad opened this issue May 29, 2020 · 0 comments · Fixed by #42
Closed

Remove AWS Provider verbiage from error messaging #24

bflad opened this issue May 29, 2020 · 0 comments · Fixed by #42
Assignees
@bflad
Labels
bug Something isn't working
Milestone
v0.5.0

Comments

@bflad
Copy link
Contributor

bflad commented May 29, 2020

Version

v0.5.0

Description

This library is shared between both the Terraform S3 Backend (currently baked into the Terraform CLI) and Terraform AWS Provider. When the "No valid credential sources" error is thrown, it is currently hardcoded to say "AWS Provider":

terraform {
  backend "s3" {
    bucket = "example"
    key    = "example"
    region = "us-east-1"
  }
}
$ terraform init
Error: No valid credential sources found for AWS Provider.
	Please see https://terraform.io/docs/providers/aws/index.html for more information on
	providing credentials for the AWS Provider

References
@bflad bflad added the bug Something isn't working label May 29, 2020
@bflad bflad added this to the v0.6.0 milestone May 29, 2020
@bflad bflad self-assigned this May 29, 2020
@bflad bflad mentioned this issue Jun 1, 2020
Merged
@bflad bflad linked a pull request Jun 2, 2020 that will close this issue
Update messaging, it is used in the backend also #31
Merged
@bflad bflad removed a link to a pull request Jun 3, 2020
Update messaging, it is used in the backend also #31
Merged
bflad added a commit that referenced this issue Jun 3, 2020
@bflad
Introduce Go 1.13 compatible error types
5d1fea5 
Reference: #24

Callers can configure their name and documentation URL to properly customize the error messaging.
@bflad bflad mentioned this issue Jun 3, 2020
Merged
bflad added a commit that referenced this issue Jun 3, 2020
@bflad
Introduce Go 1.13 compatible error types
f6fd304 
Reference: #24

Callers can configure their name and documentation URL to properly customize the error messaging.
@bflad bflad closed this as completed in #42 Jun 3, 2020
bflad added a commit that referenced this issue Jun 3, 2020
@bflad
Introduce Go 1.13 compatible error types (#42)
d39283b 
* Introduce Go 1.13 compatible error types

Reference: #24

Callers can configure their name and documentation URL to properly customize the error messaging.

* Add is error type helpers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bflad bflad

Labels
bug Something isn't working
Projects
None yet
Milestone
v0.5.0
Development

Successfully merging a pull request may close this issue.

Introduce Go 1.13 compatible error types hashicorp/aws-sdk-go-base
1 participant
@bflad