[major] Avoid usage of an additional variable to install Manage foundation #1673
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.
Issue
MASCORE-7612
Description
We are removing the need of setting an specific IS_FULL_MANAGE variable when installing Manage Foundation.
This change will ensure that by default foundation is always installed if no components is set for Manage installation.
To keep compatibility with current behavior we are also change Manage oneclick playbook to always install Manage base e the env var is not set. The way to install foundation explicitly using the playbook is by setting the attribute as:
--manage-components ""
In case someone is trying to install MAS 9.0.x with --manage-components "", we flag an error as it is not allowed anymore.
Test Results
I ran all sort of possible tests for this playbook including: