Bug: Picking wrong container registry during docker login in post Deployment pod

[ajaydevtron]

📜 Description

We have created Application A and subsequently developed Application B, which is linked to Application A. Now, we have configured post-deployments in Application B and it is utilizing its base container registry of build configuration instead of resorting to the parent override container registry.

👟 Reproduction steps

1. Create an Application (A)
2. Create an Application B which linked the app A.
3. Add post deployment stage for application B for any environment and override the container registry of parent CI .

👍 Expected behavior

It should pick the parent CI container registry during docker login in post deployment of application B.

👎 Actual Behavior

Currently it is picking base container registry of application B.

☸ Kubernetes version

1.25

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

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

• [X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• [X] I have read the Code of Conduct

AB#8483