DB projects - optionally use YAML for configuration #552
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the 9 single-instance database projects, switch from optionally using the vagrant-env plugin for configuration to optionally using YAML. The vagrant-env plugin is no longer maintained, and doesn't work correctly with Vagrant 2.4.3+ without modifying the dotenv gem. See oracle#551. The changes are the same for each project. .env/config.yaml: - rename .env to config.yaml and convert to YAML - remove comment referring to the vagrant-env plugin - update comment referring to .env/.env.local to refer to config.yaml/config.local.yaml .gitignore: - remove .env.local* and add config.local*.yaml README.md: - remove references to the vagrant-env plugin - replace references to .env/.env.local with references to config.yaml/config.local.yaml Vagrantfile: - remove references to the vagrant-env plugin - add "require 'yaml'" - replace the code that loads environment variables from .env files with code that loads environment variables from .yaml files Tested with both VirtualBox and libvirt providers. Signed-off-by: Paul Neumann <38871902+PaulNeumann@users.noreply.github.com>
oracle-contributor-agreement
bot
added
the
OCA Verified
gvenzl
approved these changes
Sep 4, 2025
Member
|
Thanks a lot for your contributions, @PaulNeumann! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the 9 single-instance database projects, switch from optionally using the vagrant-env plugin for configuration to optionally using YAML. The vagrant-env plugin is no longer maintained, and doesn't work correctly with Vagrant 2.4.3+ without modifying the dotenv gem. See #551.
The changes are the same for each project.
.env/config.yaml:.envtoconfig.yamland convert to YAML.env/.env.localto refer toconfig.yaml/config.local.yaml.gitignore:.env.local*and addconfig.local*.yamlREADME.md:.env/.env.localwith references toconfig.yaml/config.local.yamlVagrantfile:require 'yaml'.envfiles with code that loads environment variables from.yamlfilesTested with both VirtualBox and libvirt providers.
Signed-off-by: Paul Neumann 38871902+PaulNeumann@users.noreply.github.com