Skip to content

Refactor database configuration and make the main API typed#352

Merged
oranenj merged 6 commits intovoxpupuli:masterfrom
cybercom-finland:refactor-dbconfig
Apr 13, 2021
Merged

Refactor database configuration and make the main API typed#352
oranenj merged 6 commits intovoxpupuli:masterfrom
cybercom-finland:refactor-dbconfig

Conversation

@oranenj
Copy link
Copy Markdown
Contributor

@oranenj oranenj commented Apr 13, 2021

Refactors DB configuration to use a single template.

Changes PostgreSQL defaults a bit, but I'm pretty sure the default was ineffective anyway, so this is half of an API break...

@oranenj
Copy link
Copy Markdown
Contributor Author

oranenj commented Apr 13, 2021

Squashed and reworded a bit

@oranenj oranenj changed the title Use a common EPP template for dbconfig Remove $jira::use_connection_poolling and use a common template for dbconfig.xml Apr 13, 2021
@oranenj oranenj changed the title Remove $jira::use_connection_poolling and use a common template for dbconfig.xml Remove $jira::use_connection_pooling and use a common template for dbconfig.xml Apr 13, 2021
@bastelfreak bastelfreak added the backwards-incompatible This change will lead to a major version bump for the next release label Apr 13, 2021
This removes the use_connection_pooling parameter since for most
databases, it does nothing useful.

It also sets most parameters to "undef" and omits them from the
configuration if the user doesn't override them. The previous module
defaults mostly match JIRA's built-in ones anyway.
@oranenj oranenj force-pushed the refactor-dbconfig branch from a9668df to 5f0e931 Compare April 13, 2021 14:08
@oranenj
Copy link
Copy Markdown
Contributor Author

oranenj commented Apr 13, 2021

Needs another review, the changes are a bit more drastic now.

Basically, set defaults for ~everything to undef and omit them from dbconfig.xml unless specified by the user.

Also removes pool-size, I don't think it does anything, since it's not documented by Atlassian.

@oranenj oranenj force-pushed the refactor-dbconfig branch from 0062649 to 4f16e9f Compare April 13, 2021 14:39
Comment thread manifests/init.pp Outdated
@oranenj oranenj changed the title Remove $jira::use_connection_pooling and use a common template for dbconfig.xml Refactor database configuration API Apr 13, 2021
@oranenj oranenj force-pushed the refactor-dbconfig branch from 26e9e7d to 09aaa81 Compare April 13, 2021 15:25
@oranenj oranenj changed the title Refactor database configuration API Refactor database configuration and make the main API typed Apr 13, 2021
@oranenj oranenj force-pushed the refactor-dbconfig branch from d298839 to dfe1467 Compare April 13, 2021 15:59
@oranenj
Copy link
Copy Markdown
Contributor Author

oranenj commented Apr 13, 2021

I've also tested this on the Jira instance I have available and it doesn't break anything obvious, so I'll squash-merge.

@oranenj oranenj merged commit ec85b18 into voxpupuli:master Apr 13, 2021
@oranenj oranenj deleted the refactor-dbconfig branch April 13, 2021 16:19
cegeka-jenkins pushed a commit to cegeka/puppet-jira that referenced this pull request Oct 13, 2021
…i#352)

Unify dbconfig.xml across databases and use  JIRA's built-in defaults when not 
overridden by user

This removes the use_connection_pooling parameter since for most
databases, it does nothing useful. The poolsize parameter is also deprecated, and
is just an alias for pool_max_size now

It also sets  the default values for most parameters to "undef" and omits them from
the configuration if the user doesn't override them. The previous module
defaults mostly match JIRA's built-in ones anyway.

While here, add types to the main API; some things which accepted integer-looking
strings previously will now require actual integers, but otherwise nothing changes.
cegeka-jenkins pushed a commit to cegeka/puppet-jira that referenced this pull request Sep 1, 2025
…i#352)

Unify dbconfig.xml across databases and use  JIRA's built-in defaults when not 
overridden by user

This removes the use_connection_pooling parameter since for most
databases, it does nothing useful. The poolsize parameter is also deprecated, and
is just an alias for pool_max_size now

It also sets  the default values for most parameters to "undef" and omits them from
the configuration if the user doesn't override them. The previous module
defaults mostly match JIRA's built-in ones anyway.

While here, add types to the main API; some things which accepted integer-looking
strings previously will now require actual integers, but otherwise nothing changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompatible This change will lead to a major version bump for the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants