Skip to content

chore: use background hostname for admin tasks #446

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

Merged
merged 10 commits into from
Jun 25, 2024
Merged

Conversation

f0ssel
Copy link
Collaborator

@f0ssel f0ssel commented Jun 24, 2024

This adds a new getBackgroundHostName() func that is intended to be used for all SSH connections that are not the main IDE connection. This prevents background admin actions using SSH to trigger usage tracking for the workspace.

Copy link
Member

@code-asher code-asher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good!

Should we use the background host name for this one too?

.command("ssh", "-t", workspace.hostname, "cd '${workspace.idePathOnHost}' ; cd bin ; $command")

It is responsible for running the setup command (users use it to preinstall plugins, mainly) before connecting to the IDE.

@f0ssel f0ssel force-pushed the f0ssel/disable-tracking branch from 1bed23e to 632e12a Compare June 25, 2024 18:21
Base automatically changed from f0ssel/usage-app to main June 25, 2024 18:40
@f0ssel f0ssel force-pushed the f0ssel/disable-tracking branch from b8e0e29 to cf673a1 Compare June 25, 2024 18:59
Copy link
Contributor

github-actions bot commented Jun 25, 2024

Qodana Community for JVM

3 new problems were found

Inspection name Severity Problems
Incorrect string capitalization 🔶 Warning 1
Redundant nullable return type 🔶 Warning 1
String concatenation that can be converted to string template ◽️ Notice 1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.3.2
        with:
          upload-result: true
Contact Qodana team

Contact us at qodana-support@jetbrains.com

@f0ssel f0ssel requested a review from code-asher June 25, 2024 19:10
@f0ssel
Copy link
Collaborator Author

f0ssel commented Jun 25, 2024

@code-asher thanks for catching these other cases! I've updated the PR with those changes as well as got the tests all passing.

Copy link
Member

@code-asher code-asher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@f0ssel f0ssel merged commit 3e927ba into main Jun 25, 2024
6 checks passed
@f0ssel f0ssel deleted the f0ssel/disable-tracking branch June 25, 2024 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants