Contributors mailing list archives
Re: Server-tools split environment related modulesby
Hi Yannick,If there are no further objections, I'll create the repo this week-end.-sbiOn Thu, Dec 7, 2017 at 6:01 PM, Yannick Vaucher <yannick.vaucher@camptocamp.
com> wrote:Bump on this one to get a separate repositoryYannick VaucherBusiness Solutions Software DeveloperCamptocamp SAPSE A, CH-1015 LausannePhone: +41 21 619 10 30Office: +41 21 619 10 10On 30 November 2017 at 09:32, David Beal <firstname.lastname@example.org> wrote:Ok Yannick,No problem.
David BEAL - Akretion
Odoo Development / Integration2017-11-29 19:47 GMT+01:00 Yannick Vaucher <email@example.com
m>:For me it completely make sense to extract them together in an other repository. It's more maintainable and don't force people not using pip install to download them.* you can have a default config and make specifics only in some envsFor instance:It is not based on an account basis.server_environment modules and keychain are quite differentThe objective of server_environment is to have config files that setup multiple parts of odoo.* you can change existing models to change behavior of some fields depending on env* you can have different value of ir.config.parameters depending on the env.* you can create your module to set a specific field as non editable and only set by config file also depending on envWhy couldn't this also be extracted as we have 5 modules on the same topic ? server-brand has the same number of modules.Cheers,Ok,
I don't want to force anyone to use keychain ;-), that's not the purpose
just say keychain main features (from readme) are :
- All the crendentials are stored in one place: easier to manage and to audit.
- Multi-account made possible without effort.
- Store additionnal data for each account.
- Validation rules for additional data.
- Have different account for different environments (prod / test / env / etc).
Long life to server_environnement ;-)
but why in another repo if it's the topic is really near ?
I want block nothing, but we switch from 1 excess to another : too many modules by repos to too many repos with no so differentiate features.
but not a real problem for me.
my 2 cents
David BEAL - Akretion
Odoo Development / Integration+1 for splitting@David: `keychain` is another story, is for storing sensible data.Also, `server_environment` family already has a lot of children well known and used by many OCA members ;)Cheers,
David BEAL - Akretion
Odoo Development / IntegrationSorry, I didn't cross-compare the links, as mine was the GitHub issue.Well, I'm not sure if this is too much split and we are going to have a lot of repositories without too much modules. We have never used that modules as we have a Docker infrastructure that doesn't need them, and I have never like the structure with the need of that extra module (server_environment_files), but if you still continue maintaining them, then decide the best strategy.Regards.Pedro, I was refering to that split in my message, please see that I linked the same spreadsheet.On 29 November 2017 at 13:47, Pedro M. Baeza (Tecnativa) <firstname.lastname@example.org> wrote:Hi, Yannick, there's already a split in progress. See https://github.com/OCA/server-Regards.
tools/issues/1008. Look if it's enough.2017-11-29 13:32 GMT+01:00 Yannick Vaucher <email@example.com m>:modules in it's own project repository.Hello,I'm just looking for other opinions about having specific environment ('dev', 'test', 'qa', 'prod', ...)Here are the modules:mail_environmentserver_env_base_external_refer entialsserver_environment
arameterWhat about creating a OCA/server-env project ?(I propose the short env as it is clear what it means and we already have server-ux which didn't bother anyone)Here are some PR which were already made for those modules but not merged yet:It would be the right time to forward them to a new project repository.Why should we do it ?- We wanted to split the repo which dragged to many addons as being too generic.- Environment related addons might grow- it's a topic on itselfWhy we shouldn't?- we don't want too many repositories- server-environment is a well know module and has always been in server-tools(not sure there is a dedicated mailing list for server-* topic)