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

access_token config not read by provider #853

Closed
mickleroy opened this issue Jan 21, 2025 · 2 comments · Fixed by #854
Closed

access_token config not read by provider #853

mickleroy opened this issue Jan 21, 2025 · 2 comments · Fixed by #854

Comments

@mickleroy
Copy link

Describe the bug
The documentation states that the provider can be given an access_token parameter to initialise; However, this parameter doesn't seem to be getting utilised by the underlying provider implementation. Only a corresponding OCTOPUS_ACCESS_TOKEN is read.

Steps to reproduce

  1. Configure the provider to use an access token:
provider "octopusdeploy" {
  address = var.octopusServerUrl
  access_token = var.octopusAccessToken
}
  1. See the below error when planning the change:
Image

Expected behavior
The provider should initialise successfully using the access token provided.

Logs and other supporting information
See above

Screenshots
See above

Environment and versions:

  • OS: Linux
  • Octopus Server Version: Cloud
  • Terraform Version: 5.16.1
  • Octopus Terraform Provider Version: 0.39.0

Additional context
Problem line:

mjhilton added a commit that referenced this issue Jan 21, 2025
Hadn't properly mapped the value through for the framework
provider config, but seems that sdk should be fine.

fixes #853
@mjhilton
Copy link
Contributor

You're right @mickleroy, sorry for the frustration. An oversight of mine.

Will release a patch for it shortly.

@mjhilton
Copy link
Contributor

This is fixed in Release v0.40.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants