-
Notifications
You must be signed in to change notification settings - Fork 65
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #14 from gtrivedi88/HACDOCS-947
Releasing an application
- Loading branch information
Showing
2 changed files
with
23 additions
and
1 deletion.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
24 changes: 23 additions & 1 deletion
24
docs/modules/ROOT/pages/advanced-how-tos/releasing/index.adoc
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 +1,23 @@ | ||
= Releasing an application | ||
= Releasing an application | ||
:icons: font | ||
:numbered: | ||
:source-highlighter: highlightjs | ||
|
||
Two teams work together to release an application: | ||
|
||
* *Development team* - The team that develops and supports the application in a pre-production environment. | ||
* *Managed environment team* - The team that supports the production instance of that application. | ||
image::managed_environment.png[alt=Managed Environment] | ||
|
||
[1] When an application is ready for release, the Development team contacts the Managed Environment team; for example, their organization's SRE team, requesting access to the Managed environment for the first production release. | ||
|
||
[2] The Managed environment team creates the managed environment and responds to the development team with the managed environment's configuration details. The Managed environment inherits some details of the development team’s workspace. However, the development team has limited access to the production environment, which is a part of the managed environment. | ||
|
||
[3] The development team creates a matching configuration in their environment that is same as that of the Managed environment and attempts to release the application to production. | ||
|
||
[4] The Managed environment team validates the initial release and configures a traffic gateway, which allows external traffic to the application. | ||
|
||
.Next steps | ||
Create a `releasePlan` object |