Skip to content

Conversation

@jwinters01
Copy link
Contributor

followup for #26152.

  1. configures GetSources to also allow the dry source
  2. submits the dry source to getAppDetails from the frontend

note: this PR is built on top of #26152, so that PR's changes are also in here.
Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

Signed-off-by: Jonathan Winters <[email protected]>
Signed-off-by: Jonathan Winters <[email protected]>
Signed-off-by: Jonathan Winters <[email protected]>
@jwinters01 jwinters01 requested a review from a team as a code owner January 29, 2026 21:20
@bunnyshell
Copy link

bunnyshell bot commented Jan 29, 2026

❗ Preview Environment deployment failed on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

func (spec *ApplicationSpec) GetSources() ApplicationSources {
if spec.SourceHydrator != nil {
return ApplicationSources{spec.SourceHydrator.GetSyncSource()}
return ApplicationSources{spec.SourceHydrator.GetDrySource(), spec.SourceHydrator.GetSyncSource()}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This drastically change the behaviour of the function. Usually, having multiple sources returned means it is a multi-source apps. In this case, we have a single source app, and a dry-source that only applies to the hydrator. Changing this function means you should validate the behaviour of every caller, and I think it is called a lot in the codebase.

Perhaps creating a new function to return all the source for the hydrator would have a smaller blast radius.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants