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

Enhanced/improved provider configuration options and documentation #268

Merged
merged 9 commits into from
May 6, 2023

Conversation

onematchfox
Copy link
Collaborator

@onematchfox onematchfox commented Apr 27, 2023

It seems that lots of folks struggle with how to configure the provider, so I decided to try better understand the various configuration options myself and improve the documentation around this.

In doing so, I spotted a number of configuration options on the kubernetes block that were never used. So, I implemented those that could be implemented and removed those that could not be implemented.

Additionally, while delving through the argocd CLI code, I found that we can actually implement support for ArgoCD core, albeit with some restrictions/quid-pro-quos (as documented).

The outcome of all of this is, hopefully, far better documentation on the ways in which the provider can be configured (alongside examples of the varying options).

Closes #267
Closes #202
Closes #170

Partial resolution of #135

These were available on the provider configuration but not actually used,
These cannot be used by the provider so there's no point in having them here.
This does not need to be supplied when port forwarding or using local config.
@onematchfox onematchfox marked this pull request as draft April 27, 2023 11:59
Copy link
Collaborator

@oboukili oboukili left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great !

docs/index.md Outdated
# context = "foo" # Use explicit context from ArgoCD config instead of `current-context`.
}

# Unexposed ArgoCD API - using port-forwarding to temporarily expose ArgoCD API
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Unexposed ArgoCD API - using port-forwarding to temporarily expose ArgoCD API
# Unexposed ArgoCD API - using the current Kubernetes context and port-forwarding to temporarily expose ArgoCD API

@onematchfox onematchfox marked this pull request as ready for review April 27, 2023 12:18
@onematchfox
Copy link
Collaborator Author

@oboukili, quick reminder that I'm waiting on a final review here.

@onematchfox onematchfox merged commit 89a6cff into argoproj-labs:master May 6, 2023
9 checks passed
@onematchfox onematchfox deleted the feat/provider-config branch May 6, 2023 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provider authentication details/examples? Terraform block Use kube context - as argocd --core
2 participants