@@ -55,7 +55,7 @@ When the BCP is triggered due to a security incident, a thread will be opened in
| --- | --- | --- |
| Is there a financial impact? | [Handbook Page](/handbook/finance/) | #finance |
| Is there a personnel impact? | [Handbook Page](/handbook/people-group/people-ops-tech-analytics/) | #peopleops-eng |
| Is there an infrastructure impact? | [Handbook Page](/handbook/engineering/infrastructure/) | #infrastructure-lounge |
| Is there an infrastructure impact? | [Handbook Page](/handbook/engineering/infrastructure/) | #infrastructure_platforms |
| Is there a legal impact? | [Handbook Page](/handbook/legal/) | #legal |
| Is there a system impact | N/A - [Tech Stack](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/tech_stack.yml) ownership | N/A - Tech Stack technical_owner |
@@ -88,7 +88,7 @@ Please ensure that whenever you update the tech stack, you follow the instructio
| provisioner | Text in single quotes, GitLab Username | Add the username of the people in charge of provisioning access to this system, separated by commas. We require at least 2 people to be listed as provisioners of a tool. Example: '`@username`, `@username1`' | MR Author and contributors |
| deprovisioner | Text in single quotes, GitLab Username | Add the username of the people in charge of removing access to this system, separated by commas. We require at least 2 people to be listed as deprovisioners of a tool. Team members can serve as both provisioners and deprovisioners of a tool. Example: '`@username`, `@username1`' | MR Author and contributors |
| group_owner | Text | Add the group owner of the tool (team/department/function). Example: Infrastructure | MR Author and contributors |
| group_owner_slack_channel | Text | Add the Slack channel where the group owner can be reached out for help. Example: #infrastructure-lounge | MR Author and contributors |
| group_owner_slack_channel | Text | Add the Slack channel where the group owner can be reached out for help. Example: #infrastructure_platforms | MR Author and contributors |
| business_owner | Text | The Business Owner is the individual(s) responsible for all budget and decision making around the tool. They should define how the tool is used and by whom. This person(s) usually has login access to the tool as `Owner` but login access isn't necessary in all cases. Please make sure you list individual people in this field, rather than teams. Example: Jane Doe, John Doe | MR Author and contributors |
| technical_owner | Text | The Technical Owner(s) all the `administrators` of a tool. This includes everyone with the administrative clearance to provision and deprovision access of a tool and/or as the technical expertise needed to manage it. Example: Jane Doe, John Doe. See guidance [above](/handbook/business-technology/tech-stack-applications/#tech-stack-definitions) for instances where a system does not require/have an administrator function | MR Author and contributors |
| data_classification | Text (Red, Orange, Yellow, Green) or Unknown** | Decided upon by the Security team, please leave as `null` while this process is completed. More information on [Data Classification Standards](/handbook/security/policies_and_standards/data-classification-standard/).| Security Risk |
@@ -255,11 +255,11 @@ If you need assistance with a production issue or incident, please see the secti
|[#g_cells_infrastructure](https://gitlab.enterprise.slack.com/archives/C07URAK4J59) | Discussions and requests specific to the Cells Infrastructure team. |
|[#f_cells_and_organizations](https://gitlab.enterprise.slack.com/archives/C0609EXHX6F) | Channel for cross-functional discussion and coordination on Cells and Organizations. |
The SaaS Platforms group is gradually directing requests for help to the [#saas-platforms-help](https://gitlab.enterprise.slack.com/archives/C07DU5Z7V6V) Slack channel.
The SaaS Platforms group is gradually directing requests for help to the [#infrastructure-platforms](https://gitlab.enterprise.slack.com/archives/C02D1HQRTKQ) Slack channel.
This channel can be used if it is unclear which Infrastructure team the question should be directed to.
For more information, refer to the [landing page for getting assistance](/handbook/engineering/infrastructure-platforms/getting-assistance/).
The [#saas-platforms-help](https://gitlab.enterprise.slack.com/archives/C07DU5Z7V6V) channel is monitored by SaaS Platforms Engineering Managers and Staff+ engineers who triage any inbound requests. When triaging this channel, one should locate the team who can best answer this question and instruct the requestor to contact that team using the team's preferred contact method. When the requestor is connected to the right team, add a green check emoji to the message. Finally, if needed, update the [getting assistance](/handbook/engineering/infrastructure-platforms/getting-assistance/) page with any changes.
The [#infrastructure-platforms](https://gitlab.enterprise.slack.com/archives/C02D1HQRTKQ) channel is monitored by SaaS Platforms Engineering Managers and Staff+ engineers who triage any inbound requests. When triaging this channel, one should locate the team who can best answer this question and instruct the requestor to contact that team using the team's preferred contact method. When the requestor is connected to the right team, add a green check emoji to the message. Finally, if needed, update the [getting assistance](/handbook/engineering/infrastructure-platforms/getting-assistance/) page with any changes.
#### Meetings
@@ -321,7 +321,7 @@ The Engineering Manager is expected to:
### Slack to GitLab Issue Tracker Integration
In an effort to enhance the tracking and resolution of requests directed to the Infrastructure team, we are evaluating a bot that converts Slack messages in [#infrastructure_lounge](https://gitlab.slack.com/archives/CB3LSMEJV) channel into GitLab issues.
In an effort to enhance the tracking and resolution of requests directed to the Infrastructure team, we are evaluating a bot that converts Slack messages in [#infrastructure_lounge](https://gitlab.enterprise.slack.com/archives/C02D1HQRTKQ) channel into GitLab issues.
#### Workflow Overview
@@ -329,12 +329,12 @@ In an effort to enhance the tracking and resolution of requests directed to the
-**Issue Creation**: The Slack bot then creates an issue with the acknowledging agent assigned to it.
-**Thread Attachment**: The Slack thread corresponding to the message is also posted on the created GitLab issue.
-**Label Assignment**: Agents can further categorize issues by adding label emojis (`ops`, `foundations`, `observability`) in the Slack message. This action automatically assigns the issue to the respective team: Ops, Foundations, Observability.
-**Project Tracking**: These converted issues are tracked under a dedicated project hosted at [Infrastructure Lounge Slack Issue Tracker](https://gitlab.com/gitlab-com/gl-infra/infrastructure-lounge-slack-issue-tracker).
-**Project Tracking**: These converted issues are tracked under a dedicated project hosted at [Infrastructure Lounge Slack Issue Tracker](https://gitlab.com/gitlab-com/gl-infra/infrastructure_platforms-slack-issue-tracker).
-**Issue Closure**: Agents/Requester can close the issue when resolved by adding any of the `resolved_emojis` (`green-circle-check`,`white_check_mark`or `checked`in our case)
#### Configuration
Agents responsible for handling these issues are defined in a JSON file, which serves as a [CI/CD variable](https://ops.gitlab.net/gitlab-com/gl-infra/infrastructure-lounge-slack-issue-creator/-/settings/ci_cd). Currently, this file contains a static list of all members of the infrastructure department.
Agents responsible for handling these issues are defined in a JSON file, which serves as a [CI/CD variable](https://ops.gitlab.net/gitlab-com/gl-infra/infrastructure_platforms-slack-issue-creator/-/settings/ci_cd). Currently, this file contains a static list of all members of the infrastructure department.
### Project and Backlog Management
@@ -381,7 +381,7 @@ All team members are encouraged to schedule time for personal development. The f
- Ask for opinions in [#infrastructure-lounge](https://gitlab.slack.com/archives/CB3LSMEJV) or [#s_production_engineering](https://gitlab.enterprise.slack.com/archives/C07U6SAKS4D)
- Ask for opinions in [#infrastructure_platforms](https://gitlab.enterprise.slack.com/archives/C02D1HQRTKQ) or [#s_production_engineering](https://gitlab.enterprise.slack.com/archives/C07U6SAKS4D)
- Open a change management issue, err on the side of caution.
