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

An integration layer database table to link Intents and Services #393

Closed
11 tasks
turnerrainer opened this issue Feb 23, 2024 · 2 comments · Fixed by #394 or #401
Closed
11 tasks

An integration layer database table to link Intents and Services #393

turnerrainer opened this issue Feb 23, 2024 · 2 comments · Fixed by #394 or #401

Comments

@turnerrainer
Copy link
Contributor

turnerrainer commented Feb 23, 2024

AS AN Architect
I WANT TO have an integration layer database table
SO THAT links between Intents and Services could be stored there

Acceptance Criteria

  • Create a new database table called service_trigger
  • Use training_db database
  • Every change in state as a new database entry
  • Deploy all changes via Liquibase

Columns

  • ID
  • intent
  • service
  • status of type ENUM
  • Potential status values deleted, pending, declined, and approved
  • author_role of type ENUM with values trainer, service_manager, and admin
  • created as timestamp
@1AhmedYasser
Copy link
Collaborator

1AhmedYasser commented Feb 29, 2024

@turnerrainer Added Service name to trigger, so each entry should have the service id and name

@turnerrainer turnerrainer linked a pull request Feb 29, 2024 that will close this issue
@turnerrainer
Copy link
Contributor Author

Reopen to review the latest PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants