More importantly, this is a common misconception we'll need to guard against. Namely, DI extension options are NOT the same thing as a DIC parameters (and hence you can't use the parameter syntax). There'll always be some overlap (i.e. a DI extension option might just exists to be a shortcut for modifying a commonly-modified DIC parameter), but there's a little too much overlap right now, which I think adds to the confusion. Specifically, some DI extension options are set as parameters, when they really don't need to be (they're used by the DI extension and should then really be disposed of).
Spread the word :) Ryan Weaver Lead Programmer - iostudio - Nashville, TN http://www.iostudio.com http://www.thatsquality.com Twitter: @weaverryan On Mon, Feb 7, 2011 at 2:32 PM, Johannes <[email protected] > wrote: > You should simply overwrite the password directly instead of using a > parameter. > > Kind regards, > Johannes > > On 7 Feb., 17:32, Jordi Boggiano <[email protected]> wrote: > > Heya, > > > > I hit another issue today that is imo completely blocking: > > > > I define a user with a fixed password in my config.yml (I skipped some > > bits of the security config for conciseness): > > > > # config.yml > > parameters: > > admin.password: securepassword > > > > security.config: > > providers: > > main: > > users: > > admin: { password: %admin.password%, roles: [] } > > > > #### > > > > Now in development I don't want to bother with my secure password, and I > > like to have admin/admin, so I tried to redefine the parameter in > > config_dev.yml: > > > > # config_dev.yml > > parameters: > > admin.password: admin > > > > #### > > > > That does not work. Somehow the extension is loaded before the > > parameters of the various files are merged. > > > > I'm not sure how to fix it, I didn't spend much time investigating, but > > I strongly believe it should be fixed one way or the other. Or is this > > normal and everyone is happy? > > > > Cheers > > > > -- > > Jordi Boggiano > > @seldaek ::http://seld.be/ > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
