-
Notifications
You must be signed in to change notification settings - Fork 131
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: configure Segment plugin to be able to send data to Red Hat (enabled by default) #1028
Conversation
The image is available at: |
c5f392c
to
46fdb5d
Compare
The image is available at: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of a chore
should this be a feat
since it changes default behaviour and enables "phone home" delivery of telemetry data?
.rhdh/docker/Dockerfile
Outdated
@@ -229,6 +229,11 @@ ENV CHOKIDAR_USEPOLLING='1' CHOKIDAR_INTERVAL='10000' | |||
# To avoid running scripts when using `npm pack` to install dynamic plugins | |||
ENV NPM_CONFIG_ignore-scripts='true' | |||
|
|||
# Segment key for production | |||
#TODO | |||
ENV SEGMENT_WRITE_KEY="" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would it make sense to have the dev key enabled by default here SEGMENT_WRITE_KEY=gGVM6sYRK0D0ndVX22BOtS7NRcxPej8t
and then switch to the production key ONLY in downstream builds here?
https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/ci/sync-midstream.sh#L321
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, we can do that.
I assume that you will be doing something like sed 's/SEGMENT_WRITE_KEY=.*$/SEGMENT_WRITE_KEY=<prodkey>/'
. It would be nice to have this in place before we merge this PR. Can you please make the necessary changes to sync-midstream.sh script?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Occurs to me the only value in having one public key here and the other public key in gitlab is to obfuscate the prod key, but it's public and plain text in the container sources, so why bother?
On the other hand, if we put the prod key here as default, then we could toggle it off only for some builds downstream (eg. anything built from the main branch)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
transformation code to switch keys once we create the 1.2.x branch: https://gitlab.cee.redhat.com/rhidp/rhdh/-/merge_requests/10/diffs?commit_id=35426e292eda191d0b3ecf649695ecc416ff73a7#86d2a35e6325bba5ceaf29e203b14cd809af55fd_175_184
The image is available at: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
The image is available at: |
1 similar comment
The image is available at: |
The image is available at: |
The image is available at: |
Co-authored-by: Shipra Singh <94683525+shipsing@users.noreply.github.com>
Co-authored-by: Nick Boldt <nboldt@redhat.com>
The image is available at: |
/retest |
The image is available at: |
The image is available at: |
/retest |
Quality Gate passedIssues Measures |
The image is available at: |
/retest
|
/lgtm |
@kadel: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: invincibleJai, kadel, schultzp2020 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
This PR adds configuration for the Segment plugin to send data to Red Hat. The plugin is ENABLED by default. If user doesn't want that, the plugin needs to be disabled in the Helm or Operator configuration.
I'm having issues with this plugin when running locally. The Segment plugin fails to load correctly, and it shows a warning in the browser console (https://issues.redhat.com/browse/RHIDP-1451):
This issue is present only when running locally (
yarn start
). When running from the image, everything is OK. Because o that I don't consider this a blocker for this PR, it might be issue with local configuration.TODOs:
Which issue(s) does this PR fix
Related to: https://issues.redhat.com/browse/RHIDP-1311
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer