Skip to content

Conversation

@iamayushm
Copy link
Contributor

@iamayushm iamayushm commented Dec 20, 2022

Description

Option for changing project in Helm apps and option for assigning projects to unlinked CLI helm apps.

https://docs.google.com/document/d/1ME0dPLR7BSxLZQX_EQ7MFMeYSZHNvJ2uZtiE103Cvew/edit#
https://docs.google.com/document/d/1o_UHNUFHZFbCf0ELMzzv_AgA7fJm8gLiK0M76iHHN1k/edit

Fixes #2810

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration:-

EA mode

  1. In EA mode, check whether the option for selecting a project during app deployment is available or not.
  2. Deploy a sample app using the app store. Check that the configure tab of that app project is coming or not.
  3. Check whether the user is able to change project of above app. Option for changing project will be there in configure tab.
    Install an app using CLI.
  4. For CLI initially Project will come as “unassigned”. Check that whether user is able to change this project.
  5. After changing project, try linking this app to chart store and check that whether linking operation is successful or not.
  6. Install another CLI app.
  7. First Link this app to the Chart store and then try to assign a project. Check whether assignment operation is successful or not.

FULL mode

Repeat steps 1 to 8 for full mode.

User Permission Test (SSO will be required for testing this)

  1. Create 2 or more projects.
  2. Assign User to a particular project, environment and app.
  3. Check whether apps not belonging to projects, environments and app are visible to the user or not.
  4. If the user has manager access to a particular app, then check whether he is able to do every operation on that app, i.e update the app, view all tabs, etc.
  5. If the user has view access then check whether he is able to view all tabs for that app but can not update that app.
  6. If a user is changing a project for an app then make sure that he has access to both projects, current project and the updated project.

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?


@gitguardian
Copy link

gitguardian bot commented Dec 20, 2022

⚠️ GitGuardian has uncovered 7 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id Secret Commit Filename
141558 Generic High Entropy Secret 42a2e9c scripts/devtron-reference-helm-charts/deployment-chart_1-0-0/env-values.yaml View secret
2763127 Generic High Entropy Secret 42a2e9c scripts/devtron-reference-helm-charts/deployment-chart_1-0-0/secrets-test-values.yaml View secret
5236769 Generic High Entropy Secret 42a2e9c scripts/devtron-reference-helm-charts/deployment-chart_1-0-0/test-values.json View secret
141558 Generic High Entropy Secret 52b4858 scripts/devtron-reference-helm-charts/deployment-chart_1-0-0/env-values.yaml View secret
2763127 Generic High Entropy Secret 52b4858 scripts/devtron-reference-helm-charts/deployment-chart_1-0-0/secrets-test-values.yaml View secret
141558 Generic High Entropy Secret 6c405f2 scripts/devtron-reference-helm-charts/cronjob-chart_1-4-0/env-values.yaml View secret
2763127 Generic High Entropy Secret 6c405f2 scripts/devtron-reference-helm-charts/cronjob-chart_1-4-0/secrets-test-values.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

vikramdevtron
vikramdevtron previously approved these changes Dec 22, 2022
vikramdevtron
vikramdevtron previously approved these changes Jan 13, 2023
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 11 Code Smells

No Coverage information No Coverage information
10.5% 10.5% Duplication

@iamayushm iamayushm merged commit 851c54b into main Jan 16, 2023
@iamayushm iamayushm deleted the project_field_cli_helm_apps branch January 16, 2023 04:27
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.

Feature: Project selector for helms including linked/ unlinked cli helm apps.

4 participants