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.

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

Remove hardcoded default memory configuration #194

Merged
merged 2 commits into from
Jul 26, 2021
Merged

Conversation

reidmv
Copy link
Contributor

@reidmv reidmv commented Jul 23, 2021

A long time ago these settings were added to faciliate local development
on VirtualBox, using developer workstations. We should not provide
different memory defaults for PE installs than what is provided by PE
itself.

Additional fix: found Puppet Strings bug which prevented generating a
REFERENCE.md file. It is now possible to use Puppet Strings to generate
a REFERENCE.md.

A long time ago these settings were added to faciliate local development
on VirtualBox, using developer workstations. We should not provide
different memory defaults for PE installs than what is provided by PE
itself.

Additional fix: found Puppet Strings bug which prevented generating a
REFERENCE.md file. It is now possible to use Puppet Strings to generate
a REFERENCE.md.
@reidmv reidmv requested a review from a team as a code owner July 23, 2021 23:02
@@ -16,23 +15,26 @@ function peadm::generate_pe_conf (
# Define the configuration settings that will be placed in pe.conf by
# default. These can be overriden by user-supplied values in the $settings
# hash.
#
# At this time, there are no defaults which need to be modified from the
# out-of-box defaults.
$defaults = {
Copy link
Contributor

Choose a reason for hiding this comment

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

If no one is using this, and there are no use-cases in the near future ... should we remove the whole $defaults hash definition?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought about it, but wondered if there was value in keeping the structure there as scaffolding to save us a little time in the event a future change forces us back into setting some defaults. It doesn't feel like it costs anything to keep it.

Removing for now as there is no need to set peadm-coded default pe.conf
configuration values.

To restore the ability to inject defaults into generated pe.conf files,
revert this commit.
Copy link
Contributor

@mcka1n mcka1n left a comment

Choose a reason for hiding this comment

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

Looks good to me! 👍

@reidmv reidmv merged commit dd1981f into main Jul 26, 2021
@reidmv reidmv deleted the dont-override-defaults branch July 26, 2021 17:50
@reidmv reidmv added the feature label Jul 26, 2021
@reidmv reidmv changed the title Remove hardcoded mem settings from default pe.conf Remove hardcoded default memory configuration Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants