Skip to content

Comments

db_password_alias changed to dataverse.db.password #7418 #7422#7459

Merged
kcondon merged 1 commit intodevelopfrom
7418-db-pw-alias
Dec 7, 2020
Merged

db_password_alias changed to dataverse.db.password #7418 #7422#7459
kcondon merged 1 commit intodevelopfrom
7418-db-pw-alias

Conversation

@pdurbin
Copy link
Member

@pdurbin pdurbin commented Dec 4, 2020

What this PR does / why we need it:

Pull request #7422 didn't include a doc change having to do with db_password_alias being renamed to dataverse.db.password.

Which issue(s) this PR closes:

None but is part of the issue that the original pull request closed: #7418

Special notes for your reviewer:

None.

Suggestions on how to test this:

Just a doc change.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No.

Is there a release notes update needed for this change?:

I don't think so. The upgrade instructions from the previous pull request explain about deleting the old alias.

Additional documentation:

None.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 19.4% when pulling 5ee7338 on 7418-db-pw-alias into ee3b4f4 on develop.

@djbrooke djbrooke added this to the 5.3 milestone Dec 7, 2020
@poikilotherm
Copy link
Contributor

poikilotherm commented Dec 7, 2020

There's also a possibility to stay with the alias as is. Just explored this. See https://docs.payara.fish/community/docs/5.2020.6/documentation/payara-server/server-configuration/var-substitution/usage-of-variables.html#examples-ver-ref, which would allow us to add a payara-expression-config.properties:

dataverse.db.password={ALIAS=db_password_alias}

It would allow for great backward compatibility, also new installations should use the new format. 😄

@poikilotherm
Copy link
Contributor

poikilotherm commented Dec 7, 2020

As requested on IRC by @pdurbin

The name change in the alias (db_password_alias -> dataverse.db.password) happened because Payara has a MicroProfile Config Source "password", which reads from the aliases store, providing the password to the DataSourceDefinition.

This way, we can provide the database password from any of the possibe mpconfig sources consistently as "dataverse.db.password". It's important to be consistent here and make a single, reusable scope for anything database related.

My above comment was about an option I discovered to provide a backward compatibility, so existing installations wouldn't have to mangle the alias store during update.

FWIW: the other password aliases are subject to change in a future version. #7000 will hopefully cover a lot more over time.

Copy link
Contributor

@landreev landreev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@poikilotherm thanks for the explanation.
@pdurbin once again - good eye, it would be confusing to keep mentioning this "db_password_alias" in the docs.

@kcondon kcondon self-assigned this Dec 7, 2020
@kcondon kcondon merged commit 0511c8a into develop Dec 7, 2020
@kcondon kcondon deleted the 7418-db-pw-alias branch December 7, 2020 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move database configuration into application

6 participants