Add Google analytics provisioning#9
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workflow-plugin-analyticswith YAML-first Google provisioning viaanalytics.google_provider,step.analytics_google_ga4_ensure, andstep.analytics_google_gtm_ensure.gocodealone-multisitedeploy.yaml / pipelines.apply wiring up to the Google API-access blocker.Design
See:
docs/plans/2026-05-26-google-analytics-provisioning-design.mdImplementation Plan
See:
docs/plans/2026-05-26-google-analytics-provisioning.mdScope Manifest
1 | Add Google analytics provisioning | Task 1, Task 2, Task 3, Task 4, Task 5, Task 6 | feat/google-analytics-provisioningVerification
GOWORK=off go test ./...— passGOWORK=off go build ./...— passplan-scope-check.sh --verify-lock ...— passcreate_property+create_web_data_streamcreate_container+create_workspace+create_gtag_configgoogle credentials are required for live GA4 ensureRuntime launch transcript
Build:
$ GOWORK=off go build ./... # exit 0Launch / representative plugin CLI calls:
$ GOWORK=off go run ./cmd/workflow-plugin-analytics --wfctl-cli analytics google ga4 ensure --account accounts/123 --property-name example.com --stream-name example.com --default-uri https://example.com --dry-run { "account": "accounts/123", "dry_run": true, "operations": [ {"name": "create_property", "status": "planned"}, {"name": "create_web_data_stream", "status": "planned"} ] } $ GOWORK=off go run ./cmd/workflow-plugin-analytics --wfctl-cli analytics google gtm ensure --account accounts/456 --container-name example.com --domain example.com --measurement-id G-ABC123 --dry-run { "account": "accounts/456", "dry_run": true, "operations": [ {"name": "create_container", "status": "planned"}, {"name": "create_workspace", "status": "planned"}, {"name": "create_gtag_config", "status": "planned"} ] }Failure-signature scrape: clean for dry-run launch; no panics, missing modules, stack traces, or permission/resource errors.
Deploy blocker
Live provisioning for
gocodealone-multisiteintentionally stops until the operator provides Google API access, account IDs, and credential secret wiring. CLI and YAML examples remaindry_run: trueuntil then.Review note
Per May 2026 workspace guidance, Copilot review is not required while it is broken; green CI is the PR gate.