Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use new Pravega configuration key names in code and documentation #411

Closed
ravisharda opened this issue Jun 26, 2020 · 0 comments · Fixed by #416
Closed

Use new Pravega configuration key names in code and documentation #411

ravisharda opened this issue Jun 26, 2020 · 0 comments · Fixed by #416
Assignees
@SrishT
Labels
kind/enhancement Enhancement of an existing feature Pravega 0.8.0 Fix by pravega 0.8.0

Comments

@ravisharda
Copy link

ravisharda commented Jun 26, 2020 •
edited
Loading

Description

Pravega pull request 4713 modified configuration key across the board. While the names are backward compatible, we should be using the new names by default now. Accordingly, code and documentation need to be modified for the operators.

For a mapping of old to new names, see this.

From an upgrade perspective, keep in mind that if both new and old names are specified, the old ones take effect.

Importance

Should-have

Location

Suggestions for an improvement
@ravisharda ravisharda added kind/enhancement Enhancement of an existing feature Pravega 0.8.0 Fix by pravega 0.8.0 labels Jun 26, 2020
@SrishT SrishT mentioned this issue Jul 3, 2020
Merged
@SrishT SrishT self-assigned this Jul 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SrishT SrishT

Labels
kind/enhancement Enhancement of an existing feature Pravega 0.8.0 Fix by pravega 0.8.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issue 411: Updating Pravega configuration key names pravega/pravega-operator
2 participants
@SrishT @ravisharda