anchor.diff:  quarkus.hibernate-orm.database.generation=drop-and-create
   ----
   
  -Note that adding a `%prod.` profile prefix the datasource properties will not make them visible to `Dev Services for PostgreSQL` but only to the application runnnig in production mode.
  -
  -Next you can write the integration test:
  +If you add the `%prod.` profile prefix, data source properties are not visible to `Dev Services for PostgreSQL` and are only observed by an application running in production mode.
  +
  +To write the integration test, use the following code sample:
   
   [source,java]
   ----
  
positive.code: Forbidden%
  ----
  
  Finally, using the user `user` works and the security context contains the principal details (username for instance).
  
  [source,shell]
  ----
  
negative.code:    }
  }
  ----
  * The source code for the `/api/admin` endpoint is similar but instead you use a `@RolesAllowed` annotation to make sure that only users granted the `admin` role can access the endpoint.
  Add a JAX-RS resource with the following `@RolesAllowed` annotation:
  +
  [source,java]
  ----
  package org.acme.security.jpa;
  