Unable to access the Codeberg API via token

[manuelprinz]

Hey, thank you for developing this provider!

I am not sure if this is a "me" issue or not, so I am posting it here because I did not see any other way to ask a question.

I tried to obtain user information (and later create a repository) on https://codeberg.org, running Forgejo (version "13.0.0-dev-651-a48dce80+gitea-1.22.0", according to https://codeberg.org/api/v1/version). My configuration looks like this:

terraform {
  required_providers {
    forgejo = {
      source  = "svalabs/forgejo"
      version = "~> 0.5.0"
    }
  }
}

provider "forgejo" {
  host = "https://codeberg.org"
}

data "forgejo_user" "me" {
  login = "<<my username here>>"
}

The token is stored in the FORGEJO_API_TOKEN environment variable as documented, which is also exported. init works fine, but plan fails with the following error message:

Planning failed. OpenTofu encountered an error while generating this plan.

│ Error: Unable to Create Forgejo API Client
│ 
│   with provider["registry.opentofu.org/svalabs/forgejo"],
│   on codeberg.tf line 1, in provider "forgejo":
│    1: provider "forgejo" {
│ 
│ An unexpected error occurred when creating the Forgejo API client. If the error is not
│ clear, please contact the provider developers.
│ 
│ Forgejo Client Error: Get "https://codeberg.org/api/v1/version": net/http: invalid header
│ field value for "Authorization"

I tested it with the latest versions of OpenTofu and HashiCorp Terraform; both pick up version 0.5.4 of the provider, and show the same error message. Modifying the example to use a var and using the api_token key leads to the same result. Testing with username/password did not work due to 2FA.

I am not sure if this is an issue with my configuration, or a problem with the provider. Any help is appreciated!

I am happy to provide any debug information needed. (I cannot contribute, unfortunately, because I do not know Go. Beyond the very basics, at least.)

P.S.: It was also a surprise to see that the provider is from SVA. I've worked with SVA in the past and really enjoyed the experience!

[acch]

Hi @manuelprinz, thank you very much for your interest in the provider - and thanks for bringing up this issue! I'm terribly sorry for not having responded earlier; currently drowning in year-end business... my apologies!

Unfortunately, I'm unable to reproduce the issue with my local setup. Here's my configuration:

terraform {
  required_providers {
    forgejo = {
      source = "svalabs/forgejo"
    }
  }
}

provider "forgejo" {
  host = "https://codeberg.org"
}

data "forgejo_user" "this" {
  login = "acch"
}

output "debug" {
  value = data.forgejo_user.this
}

I've generated an API token through the Codeberg UI, and exported it as FORGEJO_API_TOKEN. Here's the output, as expected:

$ terraform -version
Terraform v1.14.0
on linux_amd64

$ terraform apply
data.forgejo_user.this: Reading...
data.forgejo_user.this: Read complete after 0s

Changes to Outputs:
  ~ debug = {
      ~ ...
    }

You can apply this plan to save these new output values to the Terraform state,
without changing any real infrastructure.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes


Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

debug = {
  ...
}

Could you double-check that the API token you're using has the correct permissions? You'll need to include the organization, repository, and user scope - depending on which resources you'd like to manage. I've chosen the following:

Please also note that administrative privileges are required to manage users and user repositories - and these are not available to "normal" Codeberg users. You should be able to create personal repos, however...

Can you confirm the token permissions you've assigned to the FORGEJO_API_TOKEN?

[acch]

Hi @manuelprinz, did you have a chance to check the token permissions?

[manuelprinz]

Hi @acch, I am sorry for the late reply! It saw it shortly before the holidays, but forgot about it... Sorry!

I took the time now to check again: I upgraded to the current version (1.2.0), and it worked. I don't think it was the token, because I did not change that. Since it works with 1.2.0, I have no idea what was wrong with 0.5, and I am the only one with this issue, I consider it solved. (Unless you would like me to reproduce it with an old version, but I think there is little to learn from that.)

Thank you for your support and extensive reply!