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

CMP discovery doesn't get the ARGOCD_* env #13950

Closed
3 tasks done
farcaller opened this issue Jun 7, 2023 · 0 comments · Fixed by #13947
Closed
3 tasks done

CMP discovery doesn't get the ARGOCD_* env #13950

farcaller opened this issue Jun 7, 2023 · 0 comments · Fixed by #13947
Labels
bug Something isn't working component:cmp Config Management Plugin related issues

Comments

@farcaller
Copy link
Contributor

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

Forked from #13940. The plugin discovery via executing a command should get the same environment as the actual plugin execution to have the detailed context.

It'd be nice to also update the docs to explicitly state that the environment is passed through.

To Reproduce

Run env >&2; exit 1 as the discover.find.command.

Expected behavior

The env prints all the ARGOCD_* variables.

Version

2.7.4

@farcaller farcaller added the bug Something isn't working label Jun 7, 2023
@ishitasequeira ishitasequeira added the component:cmp Config Management Plugin related issues label Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component:cmp Config Management Plugin related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants