Skip to content

Conversation

@MD-Suhad
Copy link

Description

This update adds automatic initialization of default roles during the first application startup.

When the application runs for the first time, required roles (e.g., ROLE_USER, ROLE_ADMIN) are automatically inserted into the database if they do not already exist.

This removes the need for manual database role setup.

Fixes # (issue)

Type of change

[x] New feature (non-breaking change which adds functionality)

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Ran the application locally.
  • Verified that roles are automatically created in the database on first startup.
  • Restarted the application to confirm roles are not duplicated.

Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings or errors

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Thanks so much @MD-Suhad for creating your first PR, the Spring-Boot-Blog-REST-API community thanks you :)

@gitguardian
Copy link

gitguardian bot commented Feb 11, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic Password a8bd205 src/main/resources/application.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

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