Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DEVX-3103] Migrate repository configuration from OpsLevel to Port #20

Merged
merged 1 commit into from
Dec 11, 2024
Merged

[DEVX-3103] Migrate repository configuration from OpsLevel to Port #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions port-component.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
# (required) Owner must map to a valid automated-teams team name, which should be a child team of https://github.com/orgs/pleo-io/teams/automated-teams
# The team name must not include the `pleo-io/` prefix
steward: team-site-reliability-engineering

# Any tags relevant to your components and/or mandated by platform teams
tags:

# Describes type of component the repository defines.
#
# Use:
# - `type: service` for web services (moons)
# - `type: application` for downloadable software (such as an iOS/Android app,
# CLI tool, standalone executable). This also includes e.g. web apps.
# - `type: library` for software used by other components
# - `type: configuration` for repos that contain pure configuration (such as
# setup of DangerJS or Renovate).
# - `type: documentation` for repos that mostly contain documentation.
# - `type: hiring-challenge` for our hiring challenges.
type: library

# (optional) Relevant repositories which are relevant to this component excluding the repository hosting this file. The current repository will be linked by default in Port.
# Example: Terraform folder which hosts the architecture definition for a backend service (moon)
# related_repositories:
# - name: pleo-io/terraform
# path: /components/moons/potato
# provider: terraform
# display_name: potato @ terraform

# (optional) Any internal or external tool linked to this application such as monitors, logs, documentation, third-party apps, etc.
# tools:
# - name: "Datadog logs: product-dev"
# url: https://app.datadoghq.eu/logs?query=env%3Aproduct-dev&agg_m=count&agg_m_source=base&agg_t=count&messageDisplay=inline&storage=hot&stream_sort=desc&viz=streams

# (optional) The notion page related to this application or owning team
# notion: https://www.notion.so/pleo/

# (optional) A linear view with issues relevant to this application or a link to the linear team for the owning team
# linear: https://linear.app/pleo/
Loading