Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: cherry-pick items for 2.19#16412

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.

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

Already on GitHub?Sign in to your account

Merged
stirby merged 8 commits intorelease/2.19fromcherries-post-freeze/2.19
Feb 3, 2025

Conversation

hugodutkaand others added8 commitsFebruary 3, 2025 22:53
Addressescoder/internal#317.## ChangesRequirements are quoted below:> how many orgs does deployment haveAdds the Organization entity to telemetry.> ensuring resources are associated with orgsAll resources that reference an org already report the org id totelemetry. Adds a test to check that.> whether org sync is configuredAdds the `IDPOrgSync` boolean field to the Deployment entity.## Implementation of the org sync checkWhile there's an `OrganizationSyncEnabled` method on the IDPSyncinterface, I decided not to use it directly and implemented acounterpart just for telemetry purposes. It's a compromise I'm not happyabout, but I found that it's a simpler approach than the alternative.There are multiple reasons:1. The telemetry package cannot statically access the IDPSync interfacedue to a circular import.2. We can't dynamically pass a reference to the`OrganizationSyncEnabled` function at the time of instantiating thetelemetry object, because our server initialization logic depends on thetelemetry object being created before the IDPSync object.3. If we circumvent that problem by passing the reference as aninitially empty pointer, initializing telemetry, then IDPSync, thenupdating the pointer to point to `OrganizationSyncEnabled`, we have torefactor the initialization logic of the telemetry object itself toavoid a race condition where the first telemetry report is performedwithout a valid reference.I actually implemented that approach in#16307, but realized I'm unable tofully test it. It changed the initialization order in the servercommand, and I wanted to test our CLI with Org Sync configured with apremium license. As far as I'm aware, we don't have the tooling to dothat. I couldn't figure out a way to start the CLI with a mock license,and I didn't want to go down further into the refactoring rabbit hole.So I decided that reimplementing the org sync checking logic is simpler.(cherry picked from commit92d22e2)
Closescoder/internal#323This PR adds an `email` field to the `data.owner` payload for workspacecreated and workspace manually updated notifications, as well as useraccount created/activated/suspended.(cherry picked from commitf651ab9)
Addressescoder/nexus#175.## Changes- Adds the `telemetry_items` database table. It's a key value store fortelemetry events that don't fit any other database tables.- Adds a telemetry report when HTML is served for the first time in`site.go`.(cherry picked from commit2ace044)
Addressescoder/nexus#116.## Core ConceptSend one final telemetry report after the user disables telemetry withthe message that the telemetry was disabled. No other information aboutthe deployment is sent in this report.This final report is submitted only if the deployment ever had telemetryon.## Changes1. Refactored how our telemetry is initialized.2. Introduced the `TelemetryEnabled` telemetry item, which allows todecide whether a final report should be sent.3. Added the `RecordTelemetryStatus` telemetry method, which decideswhether a final report should be sent and updates the telemetry item.4. Added tests to ensure the implementation is correct.(cherry picked from commita68d115)
@stirbystirby merged commita9775fa intorelease/2.19Feb 3, 2025
32 of 34 checks passed
@stirbystirby deleted the cherries-post-freeze/2.19 branchFebruary 3, 2025 23:06
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsFeb 3, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@aslilacaslilacaslilac approved these changes

Assignees

@stirbystirby

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@stirby@aslilac@hugodutka@DanielleMaywood@EdwardAngert

[8]ページ先頭

©2009-2025 Movatter.jp