- 
                Notifications
    
You must be signed in to change notification settings  - Fork 12
 
Chore: Fix deployment types in telemetry #256
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
Conversation
The deployment repo / type is more the issue than the underlying Kubernetes platform
| 
           Short term this is going to mess with the looker data even more, but long term it should be worth it  | 
    
| 
           The backport to  To backport this PR manually, you can either: Via the sg toolUse the  sg backport -r 6.2.x -p 256Via your terminalTo backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-6.2.x 6.2.x
# Navigate to the new working tree
cd .worktrees/backport-6.2.x
# Create a new branch
git switch --create backport-256-to-6.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cd969878a3ed233b7a8f7c97f24335881998f468
# Push it to GitHub
git push --set-upstream origin backport-256-to-6.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-6.2.xIf you encouter conflict, first resolve the conflict and stage all files, then run the commands below: git cherry-pick --continue
# Push it to GitHub
git push --set-upstream origin backport-256-to-6.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-6.2.x
 Once the pull request has been created, please ensure the following: 
  | 
    
| 
           The backport to  To backport this PR manually, you can either: Via the sg toolUse the  sg backport -r 6.2.x -p 256Via your terminalTo backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-6.2.x 6.2.x
# Navigate to the new working tree
cd .worktrees/backport-6.2.x
# Create a new branch
git switch --create backport-256-to-6.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 cd969878a3ed233b7a8f7c97f24335881998f468
# Push it to GitHub
git push --set-upstream origin backport-256-to-6.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-6.2.xIf you encouter conflict, first resolve the conflict and stage all files, then run the commands below: git cherry-pick --continue
# Push it to GitHub
git push --set-upstream origin backport-256-to-6.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-6.2.x
 Once the pull request has been created, please ensure the following: 
  | 
    
Description
Linear issue REL-812: Update deployment types
Keeping env var name consistent between deployment repos
Checklist
Test plan
Test in Looker