Skip to content

Commit

Permalink
refactor: rename ./config to ./infra TDE-915 (#209)
Browse files Browse the repository at this point in the history
#### Motivation

`./config` is not the correct term for the infrastructure as code in
this repo

#### Modification

`./config` and its references have been renamed to `./infra`

#### Checklist

_If not applicable, provide explanation of why._

~~- [ ] Tests updated~~ no tests required for folder naming
- [x] Docs updated
- [x] Issue linked in Title
  • Loading branch information
MDavidson17 authored Oct 26, 2023
1 parent 0cd0914 commit bdcfd21
Show file tree
Hide file tree
Showing 19 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Topo Workflows

Topo workflows are run on a AWS EKS Cluster using [Argo Workflows](https://argoproj.github.io/argo-workflows/). The detailed configuration is available in [this repo](./config/).
Topo workflows are run on a AWS EKS Cluster using [Argo Workflows](https://argoproj.github.io/argo-workflows/). The detailed configuration is available in [this repo](./infra/).

To get setup you need access to the Argo user role inside the EKS cluster, you will need to contact someone from Topo Data Engineering to get access, all Imagery maintainers will already have access.

Expand Down
2 changes: 1 addition & 1 deletion cdk.json
Original file line number Diff line number Diff line change
@@ -1 +1 @@
{ "app": "npx tsx config/cdk.ts" }
{ "app": "npx tsx infra/cdk.ts" }
2 changes: 1 addition & 1 deletion cdk8s.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
app: npx tsx config/cdk8s.ts
app: npx tsx infra/cdk8s.ts
language: typescript
imports:
- https://raw.githubusercontent.com/aws/karpenter/main/pkg/apis/crds/karpenter.sh_provisioners.yaml
Expand Down
4 changes: 2 additions & 2 deletions docs/concurrency.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Some workflows may need limits on how many can be run concurrently. This can
be achieved using Argo's [synchronization][1] feature.

The desired limit can be added in a ConfigMap in [config/semaphores.yml][2], e.g.
The desired limit can be added in a ConfigMap in [infra/charts/argo.semaphores.ts][2], e.g.

```yaml
apiVersion: v1
Expand Down Expand Up @@ -32,4 +32,4 @@ Any further instances which are started while two are running will be queued,
and start automatically when running workflows complete.

[1]: https://argoproj.github.io/argo-workflows/synchronization/
[2]: config/semaphores.yml
[2]: infra/charts/argo.semaphores.ts
2 changes: 1 addition & 1 deletion config/README.md → infra/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ To generate the Helm Construct for a specific Chart, follow the instructions [he

Specify the output for the imports:

`--output config/imports/`
`--output infra/imports/`

However, some of the component Helm charts do not have a `values.schema.json`. For those we won't generate any code and use the default `Helm` construct:

Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 comments on commit bdcfd21

Please sign in to comment.