[ZEE-11536] prod for palantir-foundry.yml - #67
Merged
Conversation
[ZEE-8853] draft for ellipsys-datastage.yml
cjuste
approved these changes
Jul 28, 2026
Contributor
There was a problem hiding this comment.
I'd rather put ellipsys-datastage in an other branch. And the duckdb in the datasource identifier seems strange
Author
There was a problem hiding this comment.
the fact is connector-commons needs it according to main, but it was not there... and since it's in draft...
florenta-zeenea
approved these changes
Jul 28, 2026
| identification: | ||
| keys: | ||
| - rid | ||
| - prefix |
Contributor
There was a problem hiding this comment.
shouldn't prefix positioned before rid ?
Contributor
There was a problem hiding this comment.
Suggested change
| - project_id | |
| - job_id |
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
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.
ZEE-8853 draft for ellipsys-datastage.yml
JIRA Issue
Summary
📝 Description of what was actually done as part of this PR.
QA
📝 Description of the tests to be carried out to ensure there is no regression in existing functionality.
📝 Description of the tests to be carried out to ensure the new features work correctly.
(N/A if not necessary)
Checklists
Developers
Reviewers