argocd

Argocd 🔗

applyConfig() 🔗

ApplyConfig applies a rendered config file to the cluster. The target namespace is created (server-side, kubectl apply on a Namespace doc) before the manifests are applied.

Return Type

String !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 apply-config --config-file file:path --kube-config env:MYSECRETcontent_copy Copied! 

func (m *MyModule) Example(ctx context.Context, configFile *dagger.File, kubeConfig *dagger.Secret) string  {
	return dag.
			Argocd().
			ApplyConfig(ctx, configFile, kubeConfig)
}content_copy Copied!

@function
async def example(config_file: dagger.File, kube_config: dagger.Secret) -> str:
	return await (
		dag.argocd()
		.apply_config(config_file, kube_config)
	)content_copy Copied!

@func()
async example(configFile: File, kubeConfig: Secret): Promise<string> {
	return dag
		.argocd()
		.applyConfig(configFile, kubeConfig)
}content_copy Copied!

bootstrapClusterbookCluster() 🔗

BootstrapClusterbookCluster orchestrates the full cluster-registration workflow: render the clusterbook config, optionally apply it to a cluster (–deploy), and optionally commit it to a Git repo with optional PR and merge (–commit-to-git).

Returns the rendered file so callers can also export --path=... it.

Return Type

File !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 bootstrap-clusterbook-clustercontent_copy Copied! 

func (m *MyModule) Example() *dagger.File  {
	return dag.
			Argocd().
			BootstrapClusterbookCluster()
}content_copy Copied!

@function
def example() -> dagger.File:
	return (
		dag.argocd()
		.bootstrap_clusterbook_cluster()
	)content_copy Copied!

@func()
example(): File {
	return dag
		.argocd()
		.bootstrapClusterbookCluster()
}content_copy Copied!

commitConfig() 🔗

CommitConfig commits configFile to / on in . Optionally opens a pull request against and optionally merges that PR.

Returns a multi-line summary of what was committed / opened / merged.

Return Type

String !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 commit-config --config-file file:path --repository string --git-token env:MYSECRETcontent_copy Copied! 

func (m *MyModule) Example(ctx context.Context, configFile *dagger.File, repository string, gitToken *dagger.Secret) string  {
	return dag.
			Argocd().
			CommitConfig(ctx, configFile, repository, gitToken)
}content_copy Copied!

@function
async def example(config_file: dagger.File, repository: str, git_token: dagger.Secret) -> str:
	return await (
		dag.argocd()
		.commit_config(config_file, repository, git_token)
	)content_copy Copied!

@func()
async example(configFile: File, repository: string, gitToken: Secret): Promise<string> {
	return dag
		.argocd()
		.commitConfig(configFile, repository, gitToken)
}content_copy Copied!

commitFiles() 🔗

CommitFiles commits every file in sourceDir into on in as a single commit / single push. Optionally opens a pull request against and optionally merges it.

Distinct from CommitConfig in two ways:

1. It accepts a Directory (multiple files) so callers can push e.g. cluster.yaml + kubeconfig.yaml in one commit. Two back-to-back CommitConfig calls (one file each) hit a Dagger CloneGithub cache race — the second clone is served from cache and pre-dates the first push, so git push is rejected as non-fast-forward. Bundling into one commit avoids it entirely.
2. destinationFolder is a folder (without filename); each file in sourceDir is placed under that folder. Filenames in the source directory are preserved verbatim.

Returns a multi-line summary of what was committed / opened / merged.

Return Type

String !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 commit-files --source-dir DIR_PATH --repository string --git-token env:MYSECRETcontent_copy Copied! 

func (m *MyModule) Example(ctx context.Context, sourceDir *dagger.Directory, repository string, gitToken *dagger.Secret) string  {
	return dag.
			Argocd().
			CommitFiles(ctx, sourceDir, repository, gitToken)
}content_copy Copied!

@function
async def example(source_dir: dagger.Directory, repository: str, git_token: dagger.Secret) -> str:
	return await (
		dag.argocd()
		.commit_files(source_dir, repository, git_token)
	)content_copy Copied!

@func()
async example(sourceDir: Directory, repository: string, gitToken: Secret): Promise<string> {
	return dag
		.argocd()
		.commitFiles(sourceDir, repository, gitToken)
}content_copy Copied!

createVaultIssuer() 🔗

CreateVaultIssuer prepares the cluster-side prerequisites cert-manager needs to use a remote Vault PKI as a ClusterIssuer. It does NOT create the ClusterIssuer itself — that’s the cert-manager-vault-pki AppSet’s job, which references the two Secrets this function lands on the target cluster.

What it does (in one Dagger session): 1. Decrypts the vault env yaml. 2. Talks to Vault directly (HTTP API) to upsert an ACL policy a renewable token + read the PKI CA. (No Terraform.) 3. Decrypts the target cluster’s kubeconfig. 4. Applies a 3-document YAML directly to the target cluster: - Namespace/<target-namespace> (default cert-manager) - Secret/<token-secret-name> (default cert-manager-vault-token, data.token = freshly-minted vault token) - Secret/<ca-secret-name> (default vault-pki-ca, data["ca.crt"] = live-fetched PKI root CA PEM)

Only plain core/v1 resources are created; no cert-manager CRDs, no admission-webhook coupling. The AppSet that creates the ClusterIssuer runs whenever it’s ready — order-independent.

Closes #162.

Return Type

String !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 create-vault-issuer --cluster-name string --kubeconfig-source-file file:path --vault-env-file file:path --sops-key env:MYSECRETcontent_copy Copied! 

func (m *MyModule) Example(ctx context.Context, clusterName string, kubeconfigSourceFile *dagger.File, vaultEnvFile *dagger.File, sopsKey *dagger.Secret) string  {
	return dag.
			Argocd().
			CreateVaultIssuer(ctx, clusterName, kubeconfigSourceFile, vaultEnvFile, sopsKey)
}content_copy Copied!

@function
async def example(cluster_name: str, kubeconfig_source_file: dagger.File, vault_env_file: dagger.File, sops_key: dagger.Secret) -> str:
	return await (
		dag.argocd()
		.create_vault_issuer(cluster_name, kubeconfig_source_file, vault_env_file, sops_key)
	)content_copy Copied!

@func()
async example(clusterName: string, kubeconfigSourceFile: File, vaultEnvFile: File, sopsKey: Secret): Promise<string> {
	return dag
		.argocd()
		.createVaultIssuer(clusterName, kubeconfigSourceFile, vaultEnvFile, sopsKey)
}content_copy Copied!

detectNetworkKey() 🔗

DetectNetworkKey runs kubectl get nodes -o json against the target cluster and returns the /24 prefix shared by the nodes’ InternalIP addresses (e.g. “10.31.102”). This is the format expected by render-clusterbook-cluster-config / bootstrap-clusterbook-cluster as –network-key.

When nodes span multiple /24 subnets (rare but possible with mixed pools), the most frequently observed prefix wins. IPv6 addresses are ignored.

Return Type

String !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 detect-network-key --kube-config env:MYSECRETcontent_copy Copied! 

func (m *MyModule) Example(ctx context.Context, kubeConfig *dagger.Secret) string  {
	return dag.
			Argocd().
			DetectNetworkKey(ctx, kubeConfig)
}content_copy Copied!

@function
async def example(kube_config: dagger.Secret) -> str:
	return await (
		dag.argocd()
		.detect_network_key(kube_config)
	)content_copy Copied!

@func()
async example(kubeConfig: Secret): Promise<string> {
	return dag
		.argocd()
		.detectNetworkKey(kubeConfig)
}content_copy Copied!

renderClusterbookClusterConfig() 🔗

RenderClusterbookClusterConfig renders the clusterbook-cluster-gen KCL module, which produces the manifests needed to register a cluster with Argo CD (kubeconfig Secret reference, provider config, cluster labels, optional DNS).

Values can come from a YAML/JSON file (–values-file) and/or individual CLI flags. When both are provided, CLI flags override matching keys in the file (KCL –parameters takes precedence over –parametersFile).

Returns the rendered multi-document YAML as a Dagger File.

Return Type

File !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 render-clusterbook-cluster-configcontent_copy Copied! 

func (m *MyModule) Example() *dagger.File  {
	return dag.
			Argocd().
			RenderClusterbookClusterConfig()
}content_copy Copied!

@function
def example() -> dagger.File:
	return (
		dag.argocd()
		.render_clusterbook_cluster_config()
	)content_copy Copied!

@func()
example(): File {
	return dag
		.argocd()
		.renderClusterbookClusterConfig()
}content_copy Copied!

renderKubeconfigSecret() 🔗

RenderKubeconfigSecret turns a SOPS-encrypted source file (typically a cluster kubeconfig under stuttgart-things/secrets/kubeconfigs/) into a Kubernetes v1/Secret manifest. Equivalent to:

sops --decrypt <sourceFile> > kubeconfig.yaml
kubectl create secret generic <name> -n <namespace> \
  --from-file=<dataKey>=kubeconfig.yaml \
  --dry-run=client -o yaml

By default the rendered Secret is re-encrypted with SOPS using agePublicKey so it can be safely committed to git (e.g. via commit-config). Pass –encrypt=false to get the plaintext manifest for direct kubectl apply (e.g. via apply-config).

Returns the manifest as a Dagger File so it composes with apply-config and commit-config without shell round-trips.

Return Type

File !

Arguments

dagger -m github.com/stuttgart-things/blueprints/argocd@3b1c19d54aaa2769f2c856713a59e00f78372e61 call \
 render-kubeconfig-secret --source-file file:path --sops-key env:MYSECRET --name stringcontent_copy Copied! 

func (m *MyModule) Example(sourceFile *dagger.File, sopsKey *dagger.Secret, name string) *dagger.File  {
	return dag.
			Argocd().
			RenderKubeconfigSecret(sourceFile, sopsKey, name)
}content_copy Copied!

@function
def example(source_file: dagger.File, sops_key: dagger.Secret, name: str) -> dagger.File:
	return (
		dag.argocd()
		.render_kubeconfig_secret(source_file, sops_key, name)
	)content_copy Copied!

@func()
example(sourceFile: File, sopsKey: Secret, name: string): File {
	return dag
		.argocd()
		.renderKubeconfigSecret(sourceFile, sopsKey, name)
}content_copy Copied!