This repository was archived by the owner on Nov 23, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Merged
Dev #19
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fd5aa2c
chore: trigger GitOps pipeline (empty commit)
RandithaK c54947b
feat: add development frontend origin to CORS configuration
RandithaK 563f2ad
Merge pull request #18 from TechTorque-2025/CORS-Issues
RandithaK b43efd6
Merge pull request #17 from TechTorque-2025/feat/gitops-workflow
RandithaK 675c524
feat: add env_var for appointments service endpoints
RandithaK File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent env_var handling for appointments services—standardize declaration approach.
The "appointments-availability" and "service-types" services now explicitly declare
env_var: "APPOINTMENTS_SERVICE_URL", but the related "appointments" service (line 42–47) omits theenv_varfield and relies on auto-generation. This creates an inconsistency with the established pattern in the config: services sharing a backend (auth+users, services+projects, payments+invoices) all use explicitenv_vardeclarations.If auto-generation occurs for "appointments" but explicit declarations are made for "appointments-availability" and "service-types", there's a risk of env_var mismatch or confusion about which variable controls which service.
For consistency and clarity, add
env_var: "APPOINTMENTS_SERVICE_URL"to the "appointments" service as well.# Protected appointment endpoints - name: "appointments" path_prefix: "/api/v1/appointments" target_url: "http://localhost:8083" strip_prefix: "/api/v1" auth_required: true - # env_var not specified - will auto-generate: APPOINTMENTS_SERVICE_URL + env_var: "APPOINTMENTS_SERVICE_URL"Also update the comment on line 47 to be consistent with the new explicit declaration.
Also applies to: 55-55
🤖 Prompt for AI Agents