You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should modifying the app cloning behavior so that if one workflow encounters an error during the cloning process, the remaining workflows should still be cloned. Additionally, we could improved error handling to provide clearer feedback.
🎤 Pitch / Usecases
While cloning an existing application, encountered the following error while cloning a specific workflow: Error: Get "https://k8s-api-server/api/v1/namespaces/coreos?timeout=30s": dial tcp: lookup k8s-api-server- on xxxxx: no such host.
preventing the successful cloning of the remaining workflows.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
YashasviDevtron
changed the title
Feature: Modify app cloning behavior to skip the unreachable pipeline
Feature: Modify app cloning behavior to skip the unreachable pipeline while cloning application
Sep 18, 2024
🔖 Feature description
We should modifying the app cloning behavior so that if one workflow encounters an error during the cloning process, the remaining workflows should still be cloned. Additionally, we could improved error handling to provide clearer feedback.
🎤 Pitch / Usecases
While cloning an existing application, encountered the following error while cloning a specific workflow:
Error: Get "https://k8s-api-server/api/v1/namespaces/coreos?timeout=30s": dial tcp: lookup k8s-api-server- on xxxxx: no such host.
preventing the successful cloning of the remaining workflows.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: