Skip to content

feat(db): adding tls_signing_authority_url field to database#2276

Closed
sfmadrig wants to merge 1 commit into
device-management-toolkit:mainfrom
sfmadrig:adding-tls-certificate-authority-url
Closed

feat(db): adding tls_signing_authority_url field to database#2276
sfmadrig wants to merge 1 commit into
device-management-toolkit:mainfrom
sfmadrig:adding-tls-certificate-authority-url

Conversation

@sfmadrig

@sfmadrig sfmadrig commented Aug 6, 2025

Copy link
Copy Markdown
Contributor

Adding tls_signing_authority_url to database to support custom authority

  • Updating database structure in init.sql
  • Updating profile tables
  • Updating AMTConfigration model
  • Updating tlsSigningAuthority type
  • Updating profile routes
  • Updating unit tests

PR Checklist

  • Unit Tests have been added for new changes
  • API tests have been updated if applicable
  • All commented code has been removed
  • If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Adding tls_signing_authority_url to database to support custom authority

Anything the reviewer should know when reviewing this PR?

If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )

Adding tls_signing_authority_url to database to support custom authority

 - Updating database structure in init.sql
 - Updating profile tables
 - Updating AMTConfigration model
 - Updating tlsSigningAuthority type
 - Updating profile routes
 - Updating unit tests
@sfmadrig
sfmadrig marked this pull request as ready for review August 6, 2025 08:03
@sfmadrig sfmadrig closed this Aug 7, 2025
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.

1 participant