Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-1190

Write a blog capturing SBO DevTools week learnings

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False

      Owner: Architect:

      David Peraza

      Story (Required)

      As and SBO developer I will like to capture our learning during DevTools week, so that customers see SBO used in a context of CI/CD

      Background (Required)

      We learned a few things on ArgoCD and OpenShift Pipeline to make applications bind to services in a context of a CI/CD pipeline. Will be great to expose that to our customers.

      Glossary

      NA

      Out of scope

      NA

      In Scope

      NA

      Approach(Required)

      I would propose a title like: Using OpenShift tools to simplify how applications reference Cloud Services.

      In the article we can mentione how our application simulates a SOA application with multiple microservices referencing multiple cloud services. State the problem that arises when presented with a referencing matrix with a many to many relationship between microservices and cloud services. The problem is exacerbated when we are in the presence of multiple Pipeline and Development Environments. The we explain how we can address the problem to simplify the user experience using ArgoCD, OpenShift Pipelines, SBO and Cloud Services Operators. The article can be single or multi-part. Lets start with a single article we work together and then brake it where it makes sense to brake it.

      Demo requirements(Required)

      Demo already done during DevTools week, we could improve and record this demo as well and set as a reference to the blog.

      Dependencies

      NA

      Edge Case

      NA

      Acceptance Criteria

      We have one or more blogs explaining how SBO can help simplify developer experience in a CI/CD pipeline.
      We have a demo recording that can be referenced in the Blog

      QE: NAE
      Documentation: Yes, will need review by Docs team on the Blog flow.

      Upstream: NA
      Downstream: NA

      Release Notes Type: NA

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      v

      Legend

      Unknown

      Verified

      Unsatisfied

              Unassigned Unassigned
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: