Skip to content

add: WPB-25752 add multi-ingress verification script - #6

Open
mohitrajain wants to merge 3 commits into
mainfrom
multi-ingress-verification
Open

add: WPB-25752 add multi-ingress verification script#6
mohitrajain wants to merge 3 commits into
mainfrom
multi-ingress-verification

Conversation

@mohitrajain

@mohitrajain mohitrajain commented Jul 7, 2026

Copy link
Copy Markdown

add multi-ingress verification script verified for 5.25 version for wire-server and nginx-ingress-services


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

  • GitHub link to other pull request

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

…5 version for wire-server and nginx-ingress-services
@mohitrajain
mohitrajain requested a review from julialongtin as a code owner July 7, 2026 15:34
@mohitrajain mohitrajain changed the title add: WPB-25752 add multi-ingress verification script verified for 5.2… add: WPB-25752 add multi-ingress verification script Jul 9, 2026

@Veki301 Veki301 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

some changes required

print_wire_snippet() {
local d="$1"
cat <<EOF

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

this UI of this is a little misleading, I was checking all the printed fields even though some of them were actually passing, I think the prints you do, for example:

MISSING/WRONG: add cargohold.config.aws.multiIngress."nginz-https.kiwi.bochuoi.com": https://assets.kiwi.bochuoi.com

are sufficient and actually a better feedback for the user

also, something is wrong with your logic here (or maybe its intended) but you only get a printout of this for the last failing domain (if multiple had failed, only print_wire_snippet() for the last one will be shown)

lets either drop this completely or print it out with generic values and have the user fill in the blanks with MISSING/WRONG prints from, im leaning towards removal

&& ok "nginz additional_external_env_domains contains $d" \
|| fail "add $d to nginz.nginx_conf.additional_external_env_domains"

yaml_has_list_value '.cannon.nginx_conf.additional_external_env_domains' "$d" "$WIRE_VALUES" \

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

value is under .cannon.config.nginx_conf.additional_external_env_domains

&& ok "cannon additional_external_env_domains contains $d" \
|| fail "add $d to cannon.nginx_conf.additional_external_env_domains"

if yq -e 'galley.config.settings.conversationCodeURI? != null' "$WIRE_VALUES" >/dev/null 2>&1; then

@Veki301 Veki301 Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

missing trailing .
also, I don't think this check belongs on the additional domains check, since its not domain specific, rather global
you do a similar check for cargoholds s3DownloadEndpoint in the main ingress checks and print the same message, perhaps this is better fitted over there?

|| fail "set config.dns.base: $NGINX_DOMAIN"

[[ "$(yaml_get '.config.dns.https' "$NGINX_VALUES")" == "nginz-https.${NGINX_DOMAIN}" ]] \
&& ok "config.dns.https" \

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

you are missing a || fail clause here

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