-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
changed Attributes to Key Value Configurations where appropriate.
- Loading branch information
1 parent
b45ee8f
commit 66a8b8d
Showing
4 changed files
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,15 @@ | ||
### Attributes | ||
### Key Value Configurations | ||
|
||
Attributes are environment variables that need to be assigned to the _Object_. | ||
Key Value Configurations are Value Pairs for managing associative arrays assigned to the _Object_. | ||
|
||
Attributes can be assigned at multiple levels, from the Global _Domain_ down to an individual _Component_ and have a "scope." Lower level Objects can override a higher level Object. Below is the order in which Attributes can be overridden: | ||
Key Value Pairs can be assigned at multiple levels, from the Global _Domain_ down to an individual _Component_ and have a "scope." Lower level Objects can override a higher level Object. Below is the order in which Key Value Pairs can be overridden: | ||
|
||
| Object | Description | | ||
| --- | --- | | ||
| **Global** | Contains all Environment variables and any "additional attributes" set by the user when running that task. | | ||
| **Environment** | Overrides any Global variables during a deployment. | | ||
| **Application** | Overrides the _Environment_ variables during a deployment. | | ||
| **Endpoint** | Overrides the _Application_ variables during a deployment. | | ||
| **Component** | Overrides the _Application_ variables during a deployed. | ||
| **Global** | Contains all Environment variables and any "additional Key Value Pairs" set by the user when running that task. | | ||
| **Environment** | Overrides any Global Key Value Pairs during a deployment. | | ||
| **Application** | Overrides the _Environment_ Key Value Pairsduring a deployment. | | ||
| **Endpoint** | Overrides the _Application_ Key Value Pairs during a deployment. | | ||
| **Component** | Overrides the _Application_ Key Value Pairs during a deployed. | ||
|
||
Attributes can be given any Name and a Value. Use +Add to add Attributes to the table. Use Save to confirm. Use the checkbox to Delete or Edit an Attribute. | ||
Key Value Pairs can be given any Name and a Value. Use +Add to add Key Value Pairs to the table. Use Save to confirm. Use the checkbox to Delete or Edit a Key Value Pair. |