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

[Question] The overrode named values are not written back to target configuration yaml #480

Closed
kcaoca opened this issue Feb 12, 2024 · 2 comments

Comments

@kcaoca
Copy link

kcaoca commented Feb 12, 2024

Release version

v5.0.1

Question Details

In my project, I'm about to publish the artifacts to QA environment. The extractor worked well to make artifacts in the destination folder. I can see the "named values" folder with "namedValueInformation.json" file in it:
image

I then created configuration.qa.yaml file in the root to override the secret:
image

The variable key_9b298 is defined in the library as secret and I can see the value can be retrieved at "Perform namevalue secret substitution" stage:
image

image

However, at "Run publisher for QA environment" stage, I still see the named value doesn't have a value and skipped, which caused error when publishing Application Insights using this secret.
image

What am I missing? Thank you

Expected behavior

The publisher can use the variables defined in library as secret value in named values.

Actual behavior

The secret named values don't have values while the configuration yaml has overriding settings.

Reproduction Steps

See question description.

Copy link

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

@guythetechie
Copy link
Contributor

@kcaoca - your configuration.qa.yaml is incorrect. It should be namedValues, not nameValues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants