Hithomelabs/CFTunnels
5
0
Fork 3
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ISSUE-33 #97

Closed
kruti wants to merge 88 commits from kruti/CFTunnels:ISSUE-33 into main
pull from: kruti/CFTunnels:ISSUE-33
merge into: Hithomelabs:main
Conversation 0 Commits 88 Files Changed 14 +309 -33
kruti commented 2026-01-14 17:28:28 +00:00
Owner
Copy Link

Description

  • db integration
## Description - db integration
kruti added 88 commits 2026-01-14 17:28:29 +00:00
ISSUE-33: added user flow to create mapping from tunnel ingress
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m37s
Details
ccfe79f7f1
merged with main branch
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m37s
Details
e2b2cc3ead
Schema.sql uncommenting to attempt to fix breaking build
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m41s
Details
6047471ff8
Hibernate ddl set to none to fix the breaking test build issue
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m46s
Details
02dc401224
H2 database integrated for testing profile
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m32s
Details
9817d77e7f
H2 dependency added in build.gradle
Some checks failed
sample gradle build and test / build (pull_request) Failing after 1m40s
Details
1f892e449f
Mapping added in test controller to fix the breaking test
All checks were successful
sample gradle build and test / build (pull_request) Successful in 1m39s
Details
28b003a066
kruti self-assigned this 2026-01-14 17:28:37 +00:00
kruti requested review from hitanshu 2026-01-14 17:28:39 +00:00
kruti closed this pull request 2026-01-14 17:33:55 +00:00
All checks were successful
sample gradle build and test / build (pull_request) Successful in 1m39s
Required
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
hitanshu
Labels
Clear labels
  
epic
analytics
Data analytics of platform data and logs analysis.

  
epic
development
Developing new features, services. front and and back end as well as batch jobs

  
epic
devops
Epic related to CI/CD pipeline, runners, setup and workflow triggers

  
epic
infra
Epic related to infrastructure tasks, configuring hard drives, network equipment, firewalls, anything involving getting hands dirty.

  
epic
observability
Observability stack, uptime, service discovery, network, firewall, processes, resource consumption etc.

  
epic
platform
Related to authentication, authorization, keys, passwords, configs. Updates and upgrades related to platform.

  
epic
product
Issues discussing products and features come over here.

  
priority
later
To be done but can wait. Generally areas that don't want immediate attention and warrant pre-planning, analysis and/or design

  
priority
next
Not a burning issue but needs to be worked on next. Generally should not be blocked by any issue other than priority::now

  
priority
now
Immediate priority, critical for PROD go-live

  
status
acceptance
Testing results are good and issue looks good to deploy. It is a pre-deployment sign-off of test results

  
status
blocked
Need to solve another issue before this issue can be picked. The issue is blocked till the blocking issue isn't resolved

  
status
done
Issue deployment successful.

  
status
in progress
Issue has been picked up and someone is working on it.

  
status
in review
The issue has been work on but, a review has been requested, generally good to transition to this if all PRs raised require review or are reviewed.

  
status
in testing
Code review complete and issue is in testing in lower environment. P.S. This means unit tests have already been written.

  
status
ready
Issue does not have any blocker and is ready to be picked.

  
status
refine
Something working already well in PROD but a change that makes life a little more easier, like skip into in netflix. Issues that signify added convenience.

  
status
triage
Issue is requested but not scoped. Need to be added to systematically review and categorize

  
type
analysis
An issue to perform analysis, exploring deign and implementation decisions/ considerations.

  
type
bug
A bug, needs to be fixed, raised out of an incident.

  
type
hygiene
Features remain the same, makes the platform, faster, better and less-error prone. Makes developer/ system-admin life easier

  
type
mantainence
Primarily version upgrades

  
type
story
Something new, a new feature !

No Label
epic
analytics
epic
development
epic
devops
epic
infra
epic
observability
epic
platform
epic
product
priority
later
priority
next
priority
now
status
acceptance
status
blocked
status
done
status
in progress
status
in review
status
in testing
status
ready
status
refine
status
triage
type
analysis
type
bug
type
hygiene
type
mantainence
type
story
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
kruti
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hithomelabs/CFTunnels#97
No description provided.
Delete Branch "kruti/CFTunnels:ISSUE-33"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?