generated from cloudoperators/repository-template
-
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.
- Loading branch information
Showing
1 changed file
with
84 additions
and
0 deletions.
There are no files selected for viewing
84 changes: 84 additions & 0 deletions
84
architecture-decision-records/010-greenhouse-workspace-tools.md
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 |
---|---|---|
@@ -0,0 +1,84 @@ | ||
# 010-greenhouse-workstation-tools | ||
|
||
- Status: [draft] <!-- optional --> | ||
- Deciders: [HGW, Esther, Uwe] <!-- optional --> | ||
- Date: [YYYY-MM-DD when the decision was last updated] <!-- optional. To customize the ordering without relying on Git creation dates and filenames --> | ||
- Tags: [greenhouse / cloudoperators] <!-- optional --> | ||
- Technical Story: [description | ticket/issue URL] <!-- optional --> | ||
|
||
## Context and Problem Statement | ||
|
||
Provide Greenhouse operators with pre-authenticated, pre-installed CLI like hammer/screw, openstackcli, kubectl, spore, vault, u8s. | ||
Have some sort of startup logon script that scopes the user to the correct project and region. (like `setpw` on jumphost) | ||
|
||
## Decision Drivers <!-- optional --> | ||
|
||
- [driver 1, e.g., a force, facing concern, …] | ||
- [driver 2, e.g., a force, facing concern, …] | ||
- … <!-- numbers of drivers can vary --> | ||
|
||
## Considered Options | ||
|
||
- [option 1] | ||
- [option 2] | ||
- [option 3] | ||
- … <!-- numbers of options can vary --> | ||
|
||
## Decision Outcome | ||
|
||
Chosen option: "[option 1]", | ||
because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)]. | ||
|
||
### Positive Consequences <!-- optional --> | ||
|
||
- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …] | ||
- … | ||
|
||
### Negative Consequences <!-- optional --> | ||
|
||
- [e.g., compromising quality attribute, follow-up decisions required, …] | ||
- … | ||
|
||
## Pros and Cons of the Options | Evaluation of options <!-- optional --> | ||
|
||
### [option 1] | ||
|
||
[example | description | pointer to more information | …] <!-- optional --> | ||
|
||
| Decision Driver | Rating | Reason | | ||
|---------------------|--------|-------------------------------| | ||
| [decision driver a] | +++ | Good, because [argument a] | | | ||
| [decision driver b] | --- | Good, because [argument b] | | ||
| [decision driver c] | -- | Bad, because [argument c] | | ||
| [decision driver d] | o | Neutral, because [argument d] | | ||
|
||
### [option 2] | ||
|
||
[example | description | pointer to more information | …] <!-- optional --> | ||
|
||
| Decision Driver | Rating | Reason | | ||
|---------------------|--------|-------------------------------| | ||
| [decision driver a] | +++ | Good, because [argument a] | | | ||
| [decision driver b] | --- | Good, because [argument b] | | ||
| [decision driver c] | -- | Bad, because [argument c] | | ||
| [decision driver d] | o | Neutral, because [argument d] | | ||
|
||
### [option 3] | ||
|
||
[example | description | pointer to more information | …] <!-- optional --> | ||
|
||
| Decision Driver | Rating | Reason | | ||
|---------------------|--------|-------------------------------| | ||
| [decision driver a] | +++ | Good, because [argument a] | | | ||
| [decision driver b] | --- | Good, because [argument b] | | ||
| [decision driver c] | -- | Bad, because [argument c] | | ||
| [decision driver d] | o | Neutral, because [argument d] | | ||
|
||
## Related Decision Records <!-- optional --> | ||
|
||
[previous decision record, e.g., an ADR, which is solved by this one | next decision record, e.g., an ADR, which solves this one | … | pointer to more information] | ||
|
||
## Links <!-- optional --> | ||
|
||
- [Link type](link to adr) <!-- example: Refined by [xxx](yyyymmdd-xxx.md) --> | ||
- … <!-- numbers of links can vary --> |