Skip to content

Content: How To Guide - Enabling Services on TAP with SercretTemplates #2248

@gm2552

Description

@gm2552

Summary of content

A how to guide of enabling services on TAP with SecretTemplates.
This content has been reviewed as a proposal with @BrianMMcClain.

Summary of audiences

A short summary of the audience. Include:

  • TAP developers, app operators, and service operators which to offer and consume arbitrary data services on TAP.

Level of content

Level of content as it pertains to the topic proposed. Delete those not applicable.

  • 101: "Awareness / Exploration"
  • 201: "Prototyping / Deploying"

Contributor Checklist

  1. I have added a card to the GitHub Content Backlog and/or moved it to the proper column. See Content Prewriting and Ideation
  2. [x ] My content is drafted in accordance with existing style guides and best practices. See Drafting Content
  3. [x ] The front matter (metadata) is filled out completely (e.g. description, topics, tags, author, etc - as appropriate for the content type). See Drafting Content
  4. [x ] My content has been reviewed by my team for technical accuracy. See Editing Content
  5. [x ] My content has beed reviewed and edited by a copy editor. See Editing Content
  6. [x ] If applicable: I have tested my content locally and everything passes. See Testing Content

Reviewer Checklist

  • Review if the content is a good fit for the Tanzu Developer Center. See Content Prewriting and Ideation
  • There this GitHub issue has been added to the content backlog project
  • Ensure with the author that the content has been reviewed for technical accuracy.
  • Ensure with the author that the content has been through copy editing.
  • If applicable: Ensure with the author that the content has been through Legal review.
  • Review fit with the Tanzu Developer Center Style Guide and the VMware Style Guide (VMware Employees Only).
  • Ensure the front matter is filled out correctly and completely.
  • If applicable: Review additions to custom_dict.txt.
  • Ensure with the author they have reviewed the staging site for correctness. The reviewer should review this too.
  • If applicable: Review any new Team pages.
  • Optional: Ensure the author has provided copy for Social Media distribution.\
  • If contributing via Google Docs: Send the staging link to the author to review. The reviewer should review this too. Get the final 👍 from the author to push the content public.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions