chore: deprecate modules config field in ConfigTemplate action kinds
#7063
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
vvagaytsev
force-pushed
the
chore/deprecate-modules-in-config-templates
branch
from
869a06f to
8165b74
Compare
# Conflicts: # core/src/util/deprecations.ts # docs/misc/deprecations.md
|
This will be done in the scope of module-based config syntax deprecation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Deprecate the usage of the
modulesconfig field in theConfigTemplateaction kinds.Suggests the usage of the
configsfield instead.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This PR also implies the usage of the actions instead modules in the Garden configuration files. So, should this be a part of the module-deprecation PR?