Skip to content

feat: store server config in a database. #12

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

Merged
merged 11 commits into from
Mar 31, 2023
Merged

Conversation

seilagamo
Copy link
Collaborator

This PR contains the following changes:

  • Store the Jira server configuration in a database.
  • Store the Jira project configurations in a database.
  • Store the credentials to access the Jira Servers in AWS Secrets Manager.
  • Remove the check that finds in Jira if a ticket was created.
  • Add more tests.
  • Bump Go version.

@seilagamo seilagamo force-pushed the store-server-config-in-db branch 2 times, most recently from 91e9f9c to dc4771f Compare March 10, 2023 12:02
@seilagamo seilagamo force-pushed the store-server-config-in-db branch from dc4771f to 2ece918 Compare March 13, 2023 07:18
return Credentials{}, err
}

if err != nil {

Choose a reason for hiding this comment

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

The condition of this if branch can't never be true, as there is already a guard for err not being nil above.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed in commit 91f6d4f

Copy link

@manelmontilla manelmontilla left a comment

Choose a reason for hiding this comment

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

LGTM

@seilagamo seilagamo merged commit 564bb24 into master Mar 31, 2023
@seilagamo seilagamo deleted the store-server-config-in-db branch March 31, 2023 06:23
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