Skip to content

Commit

Permalink
Feature/upgrades (#88)
Browse files Browse the repository at this point in the history
* docs(tenant-readme): update to reference

* chore(argocd): update argocd crd/app v2.7.11 -> v2.8.2, argocd helm chart 5.42.2 -> 5.45.1
  • Loading branch information
fernandoataoldotcom authored Sep 8, 2023
1 parent 752e9b6 commit 9d5c283
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion generate-tenant-readmes.tf
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
locals {
argocd_app_version = "v2.7.11"
argocd_app_version = "v2.8.2"

}

Expand Down
2 changes: 1 addition & 1 deletion modules/tenant-readme/0.1.0/readme.tf
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ data "local_file" "readme" {
locals {
codespace_version = "v0.29.0"
argocd_crd_version = var.argocd_app_version
argocd_helm_chart_version = "5.42.2"
argocd_helm_chart_version = "5.45.1"
glueops_platform_version = "v0.32.0" # this also needs to be updated in the module.glueops_platform_helm_values // generate-helm-values.tf
tools_version = "v0.4.2"
}
Expand Down
6 changes: 3 additions & 3 deletions modules/tenant-readme/0.1.0/tenant-readme.md.tpl
Original file line number Diff line number Diff line change
Expand Up @@ -119,9 +119,9 @@ gh repo clone placeholder_github_owner/placeholder_repo_name

## Using the GlueOps Platform with an Example Tenant

This cluster has been deployed for the environment: `placeholder_cluster_environment` belonging to the tenant: `placeholder_tenant_key`.<br />To deploy tenant applications, ArgoCD will look for a `tenant-stack` repository at `git@github.com:placeholder_tenant_github_org_name/glueops-placeholder_tenant_key-placeholder_cluster_environment-stack.git`, a repository which contains configurations for tenant applications to deploy.
<br /><br />As of this version, the `tenant-stack` repository is not created automatically and must be deployed manually to test tenant functionality.<br /><br />An example tenant-stack repository can be found in the Antonio's Tacos [demo organization](https://github.com/antoniostacos/nonprod-stack).<br />
In addition to creating the `tenant-stack` repository, you must install the applicable github application that was used for this cluster deployment.
This cluster has been deployed for the environment: `placeholder_cluster_environment` belonging to the tenant: `placeholder_tenant_key`.<br />To deploy tenant applications, ArgoCD will look for a `deployment-configurations` repository at `git@github.com:placeholder_tenant_github_org_name/deployment-configurations.git`, a repository which contains configurations for tenant applications to deploy.
<br /><br />As of this version, the `deployment-configurations` repository is not created automatically and must be deployed manually to test tenant functionality.<br /><br />An [example deployment-configurations repository](https://github.com/GlueOps/deployment-configurations) can be found in the GlueOps organization and [documentation covering its usage](https://glueops.dev/docs/glueops-platform-administrator/configuration/glueops-deployment-configuration) is available on the GlueOps website.<br />
In addition to creating the `deployment-configurations` repository, you must install the applicable github application that was used for this cluster deployment.

<br /><br />

Expand Down

0 comments on commit 9d5c283

Please sign in to comment.