Skip to content

Conversation

@berekuk
Copy link
Contributor

@berekuk berekuk commented Jan 20, 2026

Ported code from softmax.com.

Copy link
Contributor Author

berekuk commented Jan 20, 2026


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • add-to-merge-queue - adds this PR to the back of the merge queue
  • add-to-merge-queue-as-hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions
Copy link
Contributor

🚀 Preview deployment is ready!

URL: https://observatory-preview-5000.softmax-research.net

@berekuk berekuk marked this pull request as ready for review January 20, 2026 03:56
@berekuk berekuk requested a review from nishu-builder January 20, 2026 03:56
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 35ecd97a33

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 71 to +72
- name: Configure EKS
if: github.ref == 'refs/heads/main'
if: github.ref == 'refs/heads/main' || (env.BUILD_PREVIEW == 'true' && inputs.preview_helm_values != '')

Choose a reason for hiding this comment

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

P2 Badge Configure EKS for PR-close deletes

When a PR is closed, DELETE_PREVIEW becomes true and the helm delete step runs, but this Configure EKS step only runs for main or BUILD_PREVIEW (open PRs). On a pull_request: closed event, the kubeconfig/context is never set up, so the delete will fail and leave preview releases behind. Consider including the delete path (e.g., env.DELETE_PREVIEW == 'true') in the EKS configure condition or skipping deletion without config.

Useful? React with 👍 / 👎.

release: observatory
chart: ./devops/charts/observatory
preview_helm_values: "--set host=${{ (github.event_name == 'pull_request' && github.event.action != 'closed') && format('observatory-preview-{0}.softmax-research.net', github.event.pull_request.number) || '' }}"
preview_host: "${{ (github.event_name == 'pull_request' && github.event.action != 'closed') && format('observatory-preview-{0}.softmax-research.net', github.event.pull_request.number) || '' }}"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This has to be explicit:
- I want _build-and-deploy workflow to be reusable for charts that don't have host in values.yaml (they might have zero hosts or multiple)
- reusable vars are not easy in github workflows (requires adding another job, with its implied overhead, not worth it)

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.

3 participants