Pendo Agent for Enterprise #1997
Merged
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.
Closes #1941
Removed unneeded checks when using feature flags.
Added
WEAVE_GITOPS_FEATURE_TELEMETRY
to the dev values.Turned telemetry off for the acceptance and ui-integration testing workflow.
Added the
Pendo
component from WG OSS.Added initializing telemetry (because in OSS it was moved out of a call to
NewCoreServer
, so, now it must be called separately).Added a check for the telemetry feature flag.
Removed the unused
supportMultipleFlux
prop (which probably became unused after one of the latest UI PRs in OSS).Pulled in the latest
main
branch from WG OSS.Tested it locally, everything seems to work as expected.
Notes:
dev-values-local.yaml
with setting its value to thetrue
string or just removing it from the dev value files (in enterprise. unlike OSS< telemetry is on by default unless it is explicitly set tofalse
in the value files).Then you can run the following code in the browser console, to make sure that Pendo was or was not initialized as expected:
If telemetry is on, a Pendo object will be logged tot he console. If not, it should be undefined.