Skip to content

configuration: define how application scopes are bound to components #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hongchaodeng wants to merge 1 commit into from
Closed

configuration: define how application scopes are bound to components #135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions 6.operational_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,7 @@ This section defines the instances of components to create with this operational
| `instanceName` | `string` | Y | | The name of the instance of this component. |
| `parameterValues` | [`[]ParameterValue`](#parameterValue) | N | | Overrides of parameters that are exposed by the application scope type defined in `type`. |
| `traits` | [`[]Trait`](#trait) | N | | Specifies the traits to attach to this component instance. |
| `applicationScopes` | `[]string` | N | | Specifies the application scopes to attach to this component instance. Each item is a name referenced to the defined Scopes in this configuration. |

In addition to being unique, the `instanceName` must follow these naming rules:

Expand Down