Fix spryker after deprecations removed #524
Merged
Conversation
This file contains 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
kierenevans
added
breaking
kierenevans
force-pushed
the
feature/fix-spryker
branch
from
ad7ebd7 to
3dfaef6
Compare
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.
Dynamically define attributes for per-store environment variables, rather than use a twig include. This allows us to have all environment variables written out to both docker and helm templates.
Spryker's helm values template is now the same as _base, after removing console.enabled (removed in #256), fixing resourcePrefix to use the attribute rather than workspace.name and updating the persistence attribute usage to be
pipeline.base.persistence.TODO: