Skip to content

Conversation

@iamayushm
Copy link
Contributor

@iamayushm iamayushm commented Dec 14, 2022

Description

Adding Option to choose Project while creating apps through app store in EA mode.

Fixes #

How Has This Been Tested?

  • Created a project in EA mode and checked if project is assigned or not.
  • Give User permission for assigned project and unassigned project and checked under various roles.

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?


@iamayushm iamayushm changed the title Project field in ea mode Adding Project field in EA mode for app store apps Dec 14, 2022
@iamayushm iamayushm changed the title Adding Project field in EA mode for app store apps feat: Project field in EA mode for app store apps Dec 14, 2022
@gitguardian
Copy link

gitguardian bot commented Dec 15, 2022

⚠️ GitGuardian has uncovered 3 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
🛠 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!

@iamayushm
Copy link
Contributor Author

closing this PR as this is duplicate. This PR will be fixed by #2780

@iamayushm iamayushm closed this Jan 12, 2023
@iamayushm iamayushm reopened this Jan 12, 2023
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