Code Monkey home page Code Monkey logo

docs-aws-services's Introduction

VMware Tanzu Service Broker for AWS

This repo contains the VMware Tanzu Service Broker for AWS documentation.

In this README:

Branches

Branch name Use for… Protected? Currently lives…
main v1.4.x Yes Stage and Prod
1.5 Obsolete. Okay to delete this branch. Service Broker for AWS is no longer supported. There is no plan to release v1.5. Yes not published

Partials

Cross-product partials (if any) are single sourced from the Docs Partials repository.

Contributing to documentation

If there is some documentation to add for an unreleased patch version of these docs, then create a branch off of the live branch you intend to modify and create a pull request against that branch. After the version that change is targeting is released, the pull request can be merged and will be live the next time a documentation deployment occurs.

If the documentation is meant to be target several released versions, then you will need to:

  • create a pull request for each individual minor version
  • or ask the technical writer to cherry-pick to particular branches/versions.

For instructions on how to create a pull request on a branch and instructions on how to create a pull request using a fork, see Creating a PR in the documentation team wiki.

Publishing docs

  • docworks is the main tool for managing docs used by writers.
  • docsdash is a deployment UI which manages the promotion from staging to pre-prod to production. The process below describes how to upload our docs to staging, replacing the publication with the same version.

Prepare Markdown files

  • Markdown files live in this repo.
  • Images should live in an images directory at the same level and linked with a relative link.
  • Each page requires an entry in config/toc.md for the table of contents.
  • Variables live in config/template_variables.yml.

In Docsdash

  1. Wait about 1 minute for processing to complete after uploading.

  2. Go to https://docsdash.vmware.com/deployment-stage

    There should be an entry with a blue link which says Documentation and points to staging.

Promoting to pre-prod and prod

Prerequisite Needs additional privileges - reach out to a manager on the docs team #tanzu-docs or ask a writer to do this step for you.

  1. Go to Staging publications in docsdash
    https://docsdash.vmware.com/deployment-stage

  2. Select a publication (make sure it's the latest version)

  3. Click "Deploy selected to Pre-Prod" and wait for the pop to turn green (refresh if necessary after about 10s)

  4. Go to Pre-Prod list
    https://docsdash.vmware.com/deployment-pre-prod

  5. Select a publication

  6. Click "Sign off for Release"

  7. Wait for your username to show up in the "Signed off by" column

  8. Select the publication again

  9. Click "Deploy selected to Prod"

Troubleshooting Markdown

Problem List displays as a paragraph
Symptom: Bulleted or numbered lists look fine on GitHub but display as a single paragraph in HTML.
Solution: Add a blank line after the stem sentence and before the first item in the list.
Problem List numbering is broken: every item is 1.
Symptom: Each numbered item in a list is a 1. instead of 1., 2., 3., etc
Solution: Try removing any blank newlines within each step.
Problem Code boxes not showing
Symptom: VMware publishing system doesn't accept code tags after the three back ticks.
Solution: Make sure you're not using shell or bash or console or yaml after back ticks.

Style guide

This is a word list for terminology and word usage specific to the VMware Tanzu Service Broker for AWS for docs.

docs-aws-services's People

Contributors

amohemed avatar animatedmax avatar bentarnoff avatar blgm avatar bobbygeeze avatar bsnchan avatar cf-meganmoore avatar clarafu avatar cshollingsworth avatar dprotaso avatar dsboulder avatar ghanna2017 avatar henryborys avatar ljarzynski avatar markdcunha avatar mcnichol avatar mjgutermuth avatar mlimonczenko avatar pivotal-marcela-campo avatar pspinrad avatar radaeze avatar richardjjg avatar seviet avatar snneji avatar theckkw avatar vikafed avatar xtreme-alvin-hsieh avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs-aws-services's Issues

Service Key Policies

For the section in the docs called "Service Key Policies", we don't understand the relationship for IAM users and the policies. For example, we created a user called pcf-broker-iam and attached the "PCFInstallationPolicy" to it. But the doc doesn't ask us to attach the other 4 policies (for S3, SQS, dynamo ) , so what role or user are they part of? Please clarify in the docs. Or maybe include a screen shot or table summary of what the policies and users should look like.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.