Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Workflow GET api is nulling the configMap and secret data if state is inheriting #4187

Closed
2 tasks done
tayalrishabh96 opened this issue Nov 1, 2023 · 0 comments · Fixed by #4189
Closed
2 tasks done
Assignees
Labels
bug Something isn't working pager-duty Bugs / Issues found while on pager duty

Comments

@tayalrishabh96
Copy link
Contributor

tayalrishabh96 commented Nov 1, 2023

📜 Description

It bugs out using the below workflow GET API :
curl -s "https://cd.example.com/orchestrator/core/v1beta1/application/workflow/$appId/sample?workflowId=$workflowId&environmentId=$environmentId"
Above API fails to fetch configMap and secret's data if state of that configMap and/or secret is inheriting.

👟 Reproduction steps

  1. configure and application with configmap and secret in base deployment template. By default the state of that particular configMap or secret would be ingeriting.
  2. Use workflow get API to fetch the data. The fetched json would be missing configMap's and secret's data.

👍 Expected behavior

It should have fetched the same.

👎 Actual Behavior

It nulls out the configMap and secret's data.

☸ Kubernetes version

NA

Cloud provider

NA

🌍 Browser

Chrome

🧱 Your Environment

NA

✅ Proposed Solution

NA

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

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

AB#6562

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pager-duty Bugs / Issues found while on pager duty
Projects
None yet
2 participants