You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(sdk): issue-880 avoid hard-coding to template - #887
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Refactoring or add test (improvements in base code or adds test coverage to functionality)
CI/CD or documentation update (changes to CI/CD pipeline or documentation)
Self Checklist
I ensured that I are not pushing configuration files containing sensitive information such as testing keys.
I ensured that large PR is avoided, Consider splitting if there are more than 500 line changes, In addition to line count, also consider the number of files being affected, An ideal amount is less than 10, 25-30 is generally too large with the exception of library upgrades, refactors, etc.
I ensured that If the PR is inevitably large, a short PR review meeting or discuss with reviewers will be organized.
I ensured that If the PR is to resolve a blocker, do not make unrelated changes in the same PR e.g. formatting changes, to minimize review time.
I ensured that PR is focused
I ensured that context was given in the PR description, Include a clear description of the changes
I ensured that related github issues are linked, Include screenshots if this will make the context clearer for the reviewer
I ensured that "work in progress" or "hold" labels are removed
I ensured that adherence to style guidelines
I ensured that feature flag is applied if needed
I ensured that follow secure development practices
I ensured that no secrets or sensitive data have been committed or logged
I ensured that no hardcoded values that may change depending on environment (these should be configured dynamically e.g. through environment variables, from the db etc)
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
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.
Description
Currently the request/response body passed as variables from java to template is hard-coded like:
Enhance to make variable name configurable via kraken/kraken-app/kraken-app-hub/src/main/resources/application.yaml:
Then refer the customized variable name as
Related Issue
#885
Motivation and Context
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
Self Checklist