-
Notifications
You must be signed in to change notification settings - Fork 40
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
GitOps Resources Don't Work..... #260
Comments
Yeah, I've confirmed this with the Go SDK locally. If I manually force in the x-api-key header with my PAT value from the Harness UI, I get a working request - but I'm also able to use the context WithValue auth - which seems to be what this module is doing - at least for some requests/resources. That said, it still doesn't work in TF with:
However, I'm able to hit these resources with:
I'm able to get agents, list clusters etc - I just can't use this terraform module to do it. I'm working through a fork of the package locally to figure why this isn't' working though. Initially I thought maybe the platform_api_key wasn't being passed correctly to the Go SDK for GitOps operations. However something else seems to be going wrong internally. |
Hi @steve-gray , this has been fixed. Now GitOps resources support the pat token. |
I can confirm this is working, and was able to deploy a Gitops agent. @manavjot-harness - is there a resource to configure the association between an agent and environment anywhere? |
@steve-gray No we don't have a resource for the association for agent and environment. But you can configure environments to use certain clusters from an agent. Can you please elaborate on the use case? |
I'm unable to get any of the
harness_gitops_
prefixed resources to work. It appears either the underlying Go SDK API's don't permit the use of PAT/SAT keys and require a bearer token, or that the keys aren't being passed around internally.I've tried a few options here in different directions, but ultimately we just want to have a terraform script create some Harness resources and trigger them. It seems this is potentially a trick too much though for the current state of play?
The text was updated successfully, but these errors were encountered: