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

v4.3.1 breaks owner provider configuration #678

Closed
sh0shin opened this issue Jan 27, 2021 · 2 comments · Fixed by #685
Closed

v4.3.1 breaks owner provider configuration #678

sh0shin opened this issue Jan 27, 2021 · 2 comments · Fixed by #685
Labels
Provider Type: Bug Something isn't working as documented

Comments

@sh0shin
Copy link

sh0shin commented Jan 27, 2021

Terraform Version

Terraform v0.14.5
+ provider registry.terraform.io/integrations/github v4.3.1

Affected Resource(s)

  • github_repository
  • all

Terraform Configuration Files

terraform {
  required_providers {
    github = {
      source = "integrations/github"
    }
  }
}

provider "github" {
  owner = "sh0shin"
  # token is provided via GITHUB_TOKEN environment variable
}

resource "github_repository" "sick" {
  name        = "sick"
  description = "My sick git repository"
  visibility  = "public"
}

Debug Output

https://gist.github.com/sh0shin/8faca30a9f162939fa50fcc097868112

Expected Behavior

Repository sick should be created.

Actual Behavior

Error: GET https://api.github.com/orgs/sh0shin: 404 Not Found []

  on main.tf line 11, in provider "github":
  11: provider "github" {

Steps to Reproduce

  • terraform apply
@sh0shin
Copy link
Author

sh0shin commented Jan 27, 2021

It looks like the problem is in the config.go: L100-L124 and/or L200-L220

The owner is check as an organization and an error is returned: L118-L120 and/or L215-L217

@sorensonpragmatics
Copy link

Hitting same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Provider Type: Bug Something isn't working as documented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants