Skip to content

Commit 987a8ec

Browse files
authored
Merge pull request #14 from gtrivedi88/HACDOCS-947
Releasing an application
2 parents 86244c8 + f9a115c commit 987a8ec

File tree

2 files changed

+23
-1
lines changed

2 files changed

+23
-1
lines changed
89.3 KB
Loading
Lines changed: 23 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,23 @@
1-
= Releasing an application
1+
= Releasing an application
2+
:icons: font
3+
:numbered:
4+
:source-highlighter: highlightjs
5+
6+
Two teams work together to release an application:
7+
8+
* *Development team* - The team that develops and supports the application in a pre-production environment.
9+
10+
* *Managed environment team* - The team that supports the production instance of that application.
11+
12+
image::managed_environment.png[alt=Managed Environment]
13+
14+
[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.
15+
16+
[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.
17+
18+
[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.
19+
20+
[4] The Managed environment team validates the initial release and configures a traffic gateway, which allows external traffic to the application.
21+
22+
.Next steps
23+
Create a `releasePlan` object

0 commit comments

Comments
 (0)