Project: OpenTelemetry (Observability and Analysis / Observability)
File: assets.md

This file is intended to list all the assets controlled by OpenTelemetry. - Team account: https://opentelemetry.1password.com/ https://github.com/1Password/1password-teams-open-source#opentelemetry PR: https://github.com/1Password/1password-teams-open-source/pull/364 Admins: Link: https://actuated.dev/blog/arm-ci-cncf-ampere Doc: GitHub App available for repositories to get ARM64 Actions runners. Admin: N/A. The program is managed by the CNCF and Actuated. The only available admin task is to add the GitHub App to a repository. Link: http://cncf-aws-opentelemetry.signin.aws.amazon.com/ Community account to published Lambda layers Admin: Alex Boten @codeboten & Anthony Mirabella @aneurysm9 Link: https://console.equinix.com/projects/6f1c9af6-0470-42da-8f22-59d0df245f6b Reserved bare metal machines for the community to run performance tests and other assets on Admin: Juraci Paixo Krhling @jpkrohling and OTel TC via the mailing list address Link: https://grafana.com/orgs/otelsigsecurity Used to provide an overview of open security incidents in the org and historical data on how quickly we respond to incidents Users: SIG-Security Maintainers, Technical and Governance Committees Admins: Juraci Paixo Krhling @jpkrohling & Armin Ruech @arminru Link: https://www.nuget.org/organization/OpenTelemetry All .NET SIG maintainers are administrators of this organization. Organization e-mail (cncf-opentelemetry-net-maintainers@lists.cncf.io) is owned by CNCF. Link: https://www.myget.org/feed/Packages/opentelemetry registered under the service account (cncf-opentelemetry-net-maintainers@lists.cncf.io). Individual accounts of .NET SIG maintainers are administrators of the OpenTelemetry feed. Admin: . Link: https://www.npmjs.com/settings/opentelemetry/packages Ask any of the following people if you need access Owner: Mayur Kale @mayurkale22 Admin: Daniel Dyla @dyladan Member: Bogdan Drutu @bogdandrutu Link: https://repo1.maven.org/maven2/io/opentelemetry/ Maven doesn't have the concept of an "organization account", but these individual OpenTelemetry members have been given rights to publish under `io.opentelemetry`: Link: https://pypi.org/user/opentelemetry/ Owner: Used to provide write access to public OpenTelemetry calendar. See . Link: https://groups.google.com/g/opentelemetry-calendar-contributors Owners: Members: SIG maintainers and individuals appointed by maintainers Used to automatically invite members to all OpenTelemetry calendar events, so that time is blocked on their calendars. Link: https://groups.google.com/g/opentelemetry-calendar Owners: @mtwo Used to register service accounts and as a NuGet OpenTelemetry organization e-mail. All .NET SIG maintainers are part of this list. Owned by CNCF. Admin: . Used as a service account e-mail for Ruby SIG. All Ruby SIG maintainers are moderators of this list. Owned by CNCF. Moderators: . Private mailing list for OpenTelemetry Governance Committee. All GC members AND CNCF reps (Amye Scavarda Perrin, Chris Aniszczyk, Taylor Waggoner) are on the list and are list moderators. Admin: CNCF (via ). Link: https://www.youtube.com/channel/UCHZDBZTIfdy94xMjMKz-_MA/videos Ask any of the following people if you need to manage the feed: Owners: Amye Scavarda Perrin (CNCF rep), Sergey Kanzhelev Managers: Alolita Sharma, Alan West, Austin Parker, Ben Sigelman, Eddy Nakamura Accounts cncf-opentelemetry@cncf.io cncf-opentelemetry-meeting-1@cncf.io cncf-opentelemetry-meeting-2@cncf.io cncf-opentelemetry-meeting-3@cncf.io cncf-opentelemetry-meeting-4@cncf.io Admins: Note: while the account passwords are available in the Governance Committee 1Password, logging in from a new IP address will require being a member https://lists.cncf.io/g/cncf-otel-zoomadmins with at least moderator rights so you can see pending (unapproved) messages and retrieve the One-Time Password that is sent when you log in. To join

go to that URL and click "Apply For Membership In This Group". Then ask in the for someone to approve your membership and then to give you owner rights. Link: https://zapier.com Used to automatically add links to Zoom meeting recordings to a Used to automatically add repo maintainers to new security incidents Admins: (GitHub password is available in the OpenTelemetry Governance 1Password) Accounts admin@opentelemetry.io Admins: Used to manage the OpenTelemetry community calendar Admins: Used for community Google Docs Used to manage Zoom This is not really an OpenTelemetry asset as we do not have any credentials or admin access for it. For support: Check the Open an Ask in the Slack channel Open an We publish images from CI to Docker hub using https://hub.docker.com/u/otelbot account. The bot is registered using cncf-opentelemetry-tc@lists.cncf.io email address and Technical Committee members are owners of this account. The Admin for bot security credentials for CI is @tigrannajaryan This is a community-owned bot account that you can use when automating common GitHub tasks (e.g. release automation tasks). Important: You do not need to (and should not) give this account any permissions to any OpenTelemetry repository. Link: Admins: (GitHub password and associated 2FA for the `@opentelemetrybot` account are available in the Technical Committee 1Password) The OpenTelemetry Bot addresses two common issues: Since you can't push directly to `main` from workflows (due to branch protections), the next best thing is to generate a pull request from the automation and use an account which has signed the CLA as the commit author. The OpenTelemetry Bot account has signed the CNCF CLA, and you can assign it as the commit author in your automation: ``` git config user.name opentelemetrybot git config user.email 107717825+opentelemetrybot@users.noreply.github.com ``` It is recommended to push to branch names that start with `opentelemetrybot/`, and to add a branch protection rule for `opentelemetrybot//` with the same setup as documented for . Note that branch protection rule ordering matters, so you will need to delete the `/` branch protection rule temporarily, then add the `opentelemetrybot//` branch protection rule, then add back the `/` branch protection rule. When you use the built-in `secrets.GITHUB_TOKEN` to generate a pull request from inside of a GitHub Action, workflows will not run on that new pull request without closing and re-opening it manually (this limitation is in place to prevent accidental recursive workflow runs). The OpenTelemetry GitHub organization has a GitHub Action secret named `OPENTELEMETRYBOTGITHUBTOKEN`, which is a with `public_repo` scope for the OpenTelemetry Bot that you can use to bypass this limitation. The personal access token also has `workflow` scope which is needed when merging upstream changes of `.github/workflow` files into opentelemetrybot's forks (these forks are used for automatically opening PRs against external repos). Maintainers can open an issue in the community repository to have their repository granted access to this organization secret.