-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: api: add a route to resolve a templating expression #303
Open
rbeuque74
wants to merge
2
commits into
master
Choose a base branch
from
dev/rbeuque/templating
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
CDS Report test#1193.0 ✘
|
rbeuque74
force-pushed
the
dev/rbeuque/templating
branch
from
December 21, 2021 17:43
68e8d02
to
91b4374
Compare
wI2L
reviewed
Dec 24, 2021
rbeuque74
force-pushed
the
dev/rbeuque/templating
branch
from
December 29, 2021 13:43
91b4374
to
6f4349f
Compare
rclsilver
previously approved these changes
May 3, 2022
When debugging a failed task, we often need to resolve templated value that we struggle to inspect. POST /resolution/:id/templating will execute a templating expression given as input, and returns the resolved expression as output. This route can only be used by admins. Signed-off-by: Romain Beuque <[email protected]>
rclsilver
force-pushed
the
dev/rbeuque/templating
branch
from
May 6, 2022 10:33
6f4349f
to
c617897
Compare
Signed-off-by: Thomas Bétrancourt <[email protected]>
rclsilver
force-pushed
the
dev/rbeuque/templating
branch
from
May 6, 2022 10:33
c617897
to
7c898db
Compare
richardlt
approved these changes
May 6, 2022
Note: this route should be restricted to admin users, to avoid leaking sensitive informations from resolutions. |
wI2L
requested changes
Apr 27, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Protect route.
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 kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the new behavior (if this is a feature change)?
When debugging a failed task, we often need to resolve templated value
that we struggle to inspect. POST /resolution/:id/templating will
execute a templating expression given as input, and returns the resolved
expression as output. This route can only be used by admins.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information: