Skip to content
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

Abort render-pipeline when we get a null catalog URL #14

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

simu
Copy link
Member

@simu simu commented Jan 28, 2025

Abort render-pipeline script when Lieutenant API returns no catalog URL for a cluster. This makes the failure mode more obvious than unexpected failing compile jobs for some clusters (usually with an error like "fatal: unable to access 'catalog repo': The requested URL returned error: 403".

Checklist

  • The PR has a meaningful title. It will be used to auto-generate the
    changelog.
    The PR has a meaningful description that sums up the change. It will be
    linked in the changelog.
  • PR contains a single logical change (to build a better changelog).
  • Update the documentation.
  • Categorize the PR by adding one of the following labels so it shows up
    in the correct changelog section:
    bug, enhancement, documentation, change, breaking, dependency, internal

Abort `render-pipeline` script when Lieutenant API returns no catalog
URL for a cluster. This makes the failure mode more obvious than
unexpected failing compile jobs for some clusters (usually with an error
like "fatal: unable to access '<catalog repo>': The requested URL
returned error: 403".
@simu simu added the bug Something isn't working label Jan 28, 2025
@simu simu requested a review from a team January 28, 2025 09:57
@simu simu merged commit ac6086f into main Jan 29, 2025
8 checks passed
@simu simu deleted the fix/fail-render-pipeline-on-null-catalog-url branch January 29, 2025 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants