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

Deprecate expand converter #10723

Conversation

TylerHelmuth
Copy link
Member

Description

Link to tracking issue

Fixes #

Testing

Documentation

@codeboten codeboten changed the title Deprocate expand converter Deprecate expand converter Jul 24, 2024
Copy link

codecov bot commented Jul 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.22%. Comparing base (49ea32b) to head (6afd33e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #10723      +/-   ##
==========================================
- Coverage   92.24%   92.22%   -0.03%     
==========================================
  Files         403      403              
  Lines       18720    18717       -3     
==========================================
- Hits        17268    17261       -7     
- Misses       1097     1099       +2     
- Partials      355      357       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -36,6 +38,7 @@ func newConverter(set confmap.ConverterSettings) confmap.Converter {
}
}

// Deprecated: [v0.105.0] BASH-style env var expansion is deprecated. Use `${FOO}` or `${env:FOO}` instead.
Copy link
Member

Choose a reason for hiding this comment

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

Let's first move the $$ escaping and ensure ${FOO} expansion without it?

Copy link
Member Author

Choose a reason for hiding this comment

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

@dmitryax I was testing something, but I believe my original PR will be the one to go with

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

Successfully merging this pull request may close these issues.

2 participants