Skip to content

Commit

Permalink
Fix linting issues
Browse files Browse the repository at this point in the history
  • Loading branch information
sbkok committed Jul 25, 2023
1 parent 51c10ff commit 0ac4214
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions docs/admin-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -215,13 +215,14 @@ Config has five components in `main-notification-endpoint`, `scp`, `scm`,
- `org` configures settings in case of staged multi-organization ADF deployments.
- `stage` defines the AWS Organization stage in case of staged multi-
organization ADF deployments. This is an optional setting. In enterprise-
grade deployments, it is a common practice to define an explicit dev, int and
prod AWS Organization with its own ADF instance per AWS organization. This
approach allows for well-tested and stable prod AWS Organization deployments.
If set, a matching SSM parameter `/adf/org/stage` gets created that you can
reference in your buildspec files to allow for org-specific deployments; without
hardcoding the AWS Organization stage in your buildspec. If this variable is not
set, the SSM parameter `/adf/org/stage` defaults to "none".
grade deployments, it is a common practice to define an explicit dev, int
and prod AWS Organization with its own ADF instance per AWS organization.
This approach allows for well-tested and stable prod AWS Organization
deployments. If set, a matching SSM parameter `/adf/org/stage` gets
created that you can reference in your buildspec files to allow for
org-specific deployments; without hardcoding the AWS Organization stage in
your buildspec. If this variable is not set, the SSM parameter
`/adf/org/stage` defaults to "none".

## Accounts

Expand Down

0 comments on commit 0ac4214

Please sign in to comment.