fix: helm app deployment failure

[vishal-dt]

Description

If the helm install fails during CD, re-triggering the CD gives error as
cannot re-use a name that is still in use

Fixes #3068

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

Steps to reproduce the issue is mentioned in above issue.
Steps followed to test the solution:

1. Create a CD pipeline (with Helm deployment and Manual mode)
2. Allow Environment Override
3. Modify Ports in Deployment Template in Environment Overrides

ContainerPort:
  - envoyPort: 0
    idleTimeout: 1800s
    name: app
    port: 0
    servicePort: 0
    supportStreaming: false
    useHTTP2: false

4. Trigger CD pipeline
5. 1st Failure will have a message related to invalid yaml values
6. Re-trigger CD pipeline, it will show same error message about invalid yaml values

8. Delete the Environment Overrides 9. Re-trigger the CD pipeline and the deployment should be successful

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?

NO

[anupdhiran]

Have provided comments to him offline about PR body and logger comment. Rest looks ok.

[vikramdevtron]

why we have to mark this true if app does not created

[vishal-dt]

discussed

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication