Feature: For the Multiple GitOps support feature, a new GitOps entry should be using for every new CD pipeline

[ajaydevtron]

🔖 Feature description

Currently, during the migration of GitOps from GitLab to GitHub, we used the API to handle it environment-wise. However, for new environments, the system is still using the older GitOps settings, even though it applies the new GitOps settings for new app creation.

🎤 Pitch / Usecases

During the migration of GitOps from GitLab to GitHub, we used APIs to manage the transition environment by environment. While the new GitOps settings are correctly applied when creating new applications, new environments are still defaulting to the older GitOps configuration instead of utilizing the updated settings. This discrepancy suggests that the system has been partially updated, with changes affecting application-level configurations but not environment-level defaults.

• A new API endpoint will be exposed to migrate app level configurations
• The API endpoint takes 2 user inputs
  1. Asking which GitOps provider to configure at App level, if a pipeline exist with that provider, we set that as provider or set the app configuration as not configured such that on next pipeline creation it can pick one from global
  2. User can on purpose give not configured as an option to get the global fallback behavior

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct