-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DI] Fix merging of env vars in configs #23903
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
Conversation
nicolas-grekas
commented
Aug 16, 2017
•
edited
Loading
edited
Q | A |
---|---|
Branch? | 3.3 |
Bug fix? | yes |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | #22561, #23520 |
License | MIT |
Doc PR | - |
822cb89
to
1c4af6b
Compare
Because processing configuration is done internally in I didn't find any better implementation than the one in this PR, which consist of storing processed configs when This works only if extensions do call Decoupling config processing from loading is another possibility, but that'd be asking for big changes for all bundle authors. Not worth it IMHO. PR is ready (failures are false positives.) |
1c4af6b
to
49d12f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need copious comments so that we can still understand the logic in 2 years :)
return $this->processedConfigs[] = $processor->processConfiguration($configuration, $configs); | ||
} | ||
|
||
final public function getProcessedConfigs() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/** @internal */?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so it is
49d12f7
to
00b9273
Compare
comments added, should be ready |
@@ -106,11 +106,11 @@ public function resolve() | |||
/** | |||
* Replaces "%env(FOO)%" references by their placeholder, keeping regular "%parameters%" references as is. | |||
*/ | |||
public function resolveEnvReferences() | |||
public function resolveEnvReferences(array $value) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this a BC break ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not released yet, 3.3@dev only
Merging to unlock another PR to come fixing a bug in 3.3 also. |
This PR was merged into the 3.3 branch. Discussion ---------- [DI] Fix merging of env vars in configs | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #22561, #23520 | License | MIT | Doc PR | - Commits ------- 00b9273 [DI] Fix merging of env vars in configs