Repository navigation
Conversation
- BruImporter: support vars:secret [...] bracket syntax from Bruno,
parsing comma-separated secret variable names with empty values
- BruImporter: block parser now handles both {} and [] delimiters
- loadDotEnv: merge .env values into existing environments' empty
secret variables instead of only creating a separate ".env" env
- anarchrypto: replace grep -oP (GNU-only) with sed for macOS compat
Semgrep Static Analysis
✅ No issues found. |
SpotBugs + FindSecBugs
✅ No high-priority issues. |
Security Scan Summary
✅ All security checks passed! |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 6 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
- populateEnvCombo now restores the previously selected environment instead of resetting to "(no env)", which caused variables to silently stop resolving after any env combo refresh - Reset sessionContext when environment editor saves, ensuring updated variable values are picked up on the next request
Semgrep Static Analysis
✅ No issues found. |
SpotBugs + FindSecBugs
✅ No high-priority issues. |
Security Scan Summary
✅ All security checks passed! |
The \s* after the colon in the KV regex matched newlines, causing variables with empty values (e.g. secret_key:) to swallow the next line as their value. Replace with [ \t]* to match only horizontal whitespace, keeping each key:value on its own line.
Semgrep Static Analysis
✅ No issues found. |
SpotBugs + FindSecBugs
✅ No high-priority issues. |
Security Scan Summary
✅ All security checks passed! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vars:secret [...]bracket syntax, parsing comma-separated secret variable names into EnvVariable entries with empty values{}and[]delimiters, preventing parse corruption whenvars:secret [...]blocks precede other blocks.envfile values into existing environments' empty secret variables (e.g. "qa") instead of only creating a separate ".env" environmentgrep -oP(GNU-only Perl regex) withsedfor macOS compatibilityContext
When importing a Bruno collection, secret variables (
keycloak_client_id,keycloak_client_secret, etc.) were not being resolved because:vars:secret [name1, name2]format uses[]brackets, which the block parser didn't recognize.envfile values were loaded as a separate ".env" environment instead of filling the secret placeholders in existing environments like "qa"Test plan
vars:secret [...]format -- secret variable names should appear in the environment editor.envvalues are merged into existing environments' empty secretsanarchryptolauncher works on macOS (version detection viased)./gradlew test-- all tests pass