anchor.diff:      // getter and setters
   
   }
  -```
  +----
   
   A way to see that changes effectively happen is creating another bean that prints the message periodically.
   
  -```java
  +[source,java]
  +----
   @Component
   public class MyBean {
   
  
positive.code: Let's assume that we have a spring boot application named ``demo`` that uses properties to read its database
  configuration. We can create a Kubernetes secret using the following command:
  
  ```
  oc create secret generic db-secret --from-literal=username=user --from-literal=password=p455w0rd
  ```
  
  This would create the following secret (shown using `oc get secrets db-secret -o yaml`):
  
  ```yaml
  apiVersion: v1
  data:
    password: cDQ1NXcwcmQ=
  
negative.code:       profiles: production
      greeting:
        message: Say Hello to the Ops
  
  In the above case, the configuration loaded into your Spring Application with the `development` profile will be:
  [source,yaml]
    greeting:
      message: Say Hello to the Developers
    farewell:
      message: Say Goodbye to the Developers
  
  whereas if the `production` profile is active, the configuration will be:
  [source,yaml]
    greeting:
      message: Say Hello to the Ops
    farewell:
      message: Say Goodbye
  
  If both profiles are active, the property which appears last within the configmap will overwrite preceding values.
  
  