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

chore: remove connector auth TOML files from .gitignore and .dockerignore #3330

Merged
merged 2 commits into from
Jan 11, 2024

Conversation

SanchithHegde
Copy link
Member

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

This PR fixes the -dirty suffix appearing in the x-hyperswitch-version header, only with Docker image builds but not when running locally.

Motivation and Context

As of today, on the 2024.01.11.0 Docker image running on our sandbox environment, we see a -dirty suffix in the x-hyperswitch-version header:

$ curl --silent --include https://sandbox.hyperswitch.io/health | grep 'x-hyperswitch-version:'
x-hyperswitch-version: 2024.01.11.0-dirty

This PR fixes the working directory being dirty in Docker builds, and thus the -dirty suffix appearing in the header.

How did you test it?

Built a Docker image locally and ran the built image using the following commands:

$ docker build --progress=plain --build-arg BINARY=router --tag router:latest .
$ docker run --rm --publish 8080:8080 --volume ./config:/local/config --env ROUTER__MASTER_DATABASE__HOST=host.docker.internal --env ROUTER__REDIS__HOST=host.docker.internal --env RUN_ENV=development --net=host router:latest

And then checked the version header within the container using the command:

curl --silent --include http://localhost:8080/health | grep 'x-hyperswitch-version:'

(The 2024.01.10.3 tag was something I created locally, it does not exist on GitHub.)

Screenshot of Dokcer container run

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible
  • I added a CHANGELOG entry if applicable

@SanchithHegde SanchithHegde added A-infra Area: Infrastructure C-bug Category: Bug S-waiting-on-review Status: This PR has been implemented and needs to be reviewed labels Jan 11, 2024
@SanchithHegde SanchithHegde self-assigned this Jan 11, 2024
@SanchithHegde SanchithHegde requested review from a team as code owners January 11, 2024 11:09
@SanchithHegde SanchithHegde requested a review from a team as a code owner January 11, 2024 11:35
@likhinbopanna likhinbopanna added this pull request to the merge queue Jan 11, 2024
Merged via the queue into main with commit 9f6ef3f Jan 11, 2024
9 of 11 checks passed
@likhinbopanna likhinbopanna deleted the fix-dirty-version-header-docker-builds branch January 11, 2024 14:43
@SanchithHegde SanchithHegde removed the S-waiting-on-review Status: This PR has been implemented and needs to be reviewed label Jan 11, 2024
pixincreate added a commit that referenced this pull request Jan 12, 2024
…-router

* 'main' of github.com:juspay/hyperswitch: (84 commits)
  chore(config): add merchant_secret config for webhooks for  cashtocode and volt in wasm dashboard (#3333)
  chore(version): 2024.01.12.0
  fix: update amount_capturable based on intent_status and payment flow (#3278)
  feat: add support for card extended bin in payment attempt (#3312)
  feat(connector): [cybersource] Implement 3DS flow for cards (#3290)
  chore: remove connector auth TOML files from `.gitignore` and `.dockerignore` (#3330)
  fix(refund): add merchant_connector_id in refund (#3303)
  feat(connector): [BOA/CYB] Store AVS response in connector_metadata (#3271)
  feat(outgoingwebhookevent): adding api for query to fetch outgoing webhook events log (#3310)
  feat(router): payment_method block (#3056)
  feat(connector): [Volt] Add support for refund webhooks  (#3326)
  feat(users): invite user without email (#3328)
  feat(euclid_wasm): config changes for NMI (#3329)
  refactor(router): restricted list payment method Customer to api-key based (#3100)
  feat(connector): [BOA/Cyb] Include merchant metadata in capture and void requests (#3308)
  fix(router): add config to avoid connector tokenization for `apple pay` `simplified flow` (#3234)
  refactor(router): flagged order_details validation to skip validation (#3116)
  fix(core): surcharge with saved card failure (#3318)
  feat(payment_link): Added sdk layout option payment link (#3207)
  chore(version): 2024.01.11.0
  ...
pixincreate added a commit that referenced this pull request Jan 13, 2024
* 'main' of github.com:juspay/hyperswitch: (22 commits)
  chore(version): 2024.01.12.1
  chore: add api reference for blocklist (#3336)
  chore(config): add merchant_secret config for webhooks for  cashtocode and volt in wasm dashboard (#3333)
  chore(version): 2024.01.12.0
  fix: update amount_capturable based on intent_status and payment flow (#3278)
  feat: add support for card extended bin in payment attempt (#3312)
  feat(connector): [cybersource] Implement 3DS flow for cards (#3290)
  chore: remove connector auth TOML files from `.gitignore` and `.dockerignore` (#3330)
  fix(refund): add merchant_connector_id in refund (#3303)
  feat(connector): [BOA/CYB] Store AVS response in connector_metadata (#3271)
  feat(outgoingwebhookevent): adding api for query to fetch outgoing webhook events log (#3310)
  feat(router): payment_method block (#3056)
  feat(connector): [Volt] Add support for refund webhooks  (#3326)
  feat(users): invite user without email (#3328)
  feat(euclid_wasm): config changes for NMI (#3329)
  refactor(router): restricted list payment method Customer to api-key based (#3100)
  feat(connector): [BOA/Cyb] Include merchant metadata in capture and void requests (#3308)
  fix(router): add config to avoid connector tokenization for `apple pay` `simplified flow` (#3234)
  refactor(router): flagged order_details validation to skip validation (#3116)
  fix(core): surcharge with saved card failure (#3318)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-infra Area: Infrastructure C-bug Category: Bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants