Skip to content

converter: use backticks in generated alloy for strings #3715

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kalleep
Copy link
Contributor

@kalleep kalleep commented May 28, 2025

PR Description

If we detect any double quotes we use backticks for generated string

Which issue(s) this PR fixes

Fixes: 3690

Notes to the Reviewer

PR Checklist

  • CHANGELOG.md updated
  • Documentation added
  • Tests updated
  • Config converters updated
@kalleep kalleep requested a review from a team as a code owner May 28, 2025 09:28
@@ -1,6 +1,6 @@
otelcol.receiver.otlp "default" {
grpc {
endpoint = coalesce(sys.env("NORMAL_FORMAT"), "https://www.example.com/some/file-path?query={using brackets, spaces,+'and'%20\"quotes\"}")
endpoint = `${env:NORMAL_FORMAT:-https://www.example.com/some/file-path?query={using brackets, spaces,+'and'%20"quotes"}}`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not correct

@kalleep kalleep marked this pull request as draft May 28, 2025 09:35
Copy link
Contributor

This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant