You could adjust cm to recognize a macro and expand that macro to something local like a file, a system property, or an environment variable.
That is how I solved it in the Configurer. Works very well on Travis that allows you to configure with encrypted data that is decrypted as environment variables. Peter Kriens Sent from my iPhone > On Apr 23, 2016, at 11:18 AM, Carsten Ziegeler <cziege...@apache.org> wrote: > > Antonio Sanso wrote >> hi, >> >> I would actually have the same question? >> >> Is there anything can be done here ? If not there is any plan to improve >> this? >> I might try to help out in this area providing a patch… >> >> Anyone :)? > > Didn't we discuss some time back to have a crypt service and leave it up > to every component to use this service to decrypt configuration properties? > > Automatic decryption e.g. in configuration admin is not really a good > idea, as this would mean everyone can get the configuration decrypted > and it's visible in the web console, in the status zip etc. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
