Skip to content

Commit

Permalink
Merge pull request #470 from dgraeber/fix/name-gen-docs
Browse files Browse the repository at this point in the history
adding nameGenerator docs
  • Loading branch information
dgraeber authored Dec 19, 2023
2 parents 318822c + 3688ad9 commit f814b55
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 0 deletions.
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and [Keep a Ch
### Fixes
- update `manifests/examples/` to point to an updated release branch
- Docs - manifest name description (seed-farmer/docs/source/manifests.md) needed correction
- Docs - added definition of `nameGenerator` for deployment manifest (seed-farmer/docs/source/manifests.md)

## v3.0.1 (2023-11-10)

Expand Down
11 changes: 11 additions & 0 deletions docs/source/manifests.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@ The deployment manifest is the top level manifest and resides in the `modules` d

```yaml
name: examples
nameGenerator:
prefix: myprefix
suffix:
valueFrom:
envVariable: SUFFIX_ENV_VARIABLE
toolchainRegion: us-west-2
forceDependencyRedeploy: False
groups:
Expand Down Expand Up @@ -69,6 +74,12 @@ targetAccountMappings:
```

- **name** : this is the name of your deployment. There can be only one deployment with this name in a project.
- THIS CANNOT BE USED WITH `nameGenerator`
- **nameGenerator** : this supports dynamically generating a deployment name by concatenation of the following fields:
- **prefix** - the prefix string of the name
- **suffix** - the suffix string of the name
- Both of these fields support the use of [Environment Variables](envVariable) (see example above)
- THIS CANNOT BE USED WITH `name`
- **toolchainRegion** :the designated region that the `toolchain` is created in
- **forceDependencyRedeploy**: this is a boolean that tells seedfarmer to redeploy ALL dependency modules (see [Force Dependency Redeploy](force-redeploy)) - Default is `False`
- **groups** : the relative path to the [`module manifests`](module_manifest) that define each module in the group. This sequential order is preserved in deployment, and reversed in destroy.
Expand Down

0 comments on commit f814b55

Please sign in to comment.