Skip to content
This repository was archived by the owner on Mar 1, 2023. It is now read-only.

TAS Deployment Instructions #233

Merged
merged 10 commits into from
May 22, 2020
Merged

TAS Deployment Instructions #233

merged 10 commits into from
May 22, 2020

Conversation

j-lea
Copy link
Contributor

@j-lea j-lea commented May 11, 2020

Thanks for contributing to postfacto. To speed up the process of reviewing your pull request please provide us with:

  • A short explanation of the proposed change:
    Add instructions and generate deployment script to deploy Postfacto on TAS (a rebranding of PCF) and change all references of Pivotal Cloud Foundry to just Cloud Foundry (open source).

  • An explanation of the use cases your change solves
    Allow users to easily deploy Postfacto to their own instance of TAS.

  • Links to any other associated PRs

  • I have reviewed the contributing guide

  • I have made this pull request to the master branch

  • I have run all the tests using ./test.sh.

  • I have added the copyright headers to each new file added

  • I have given myself credit in the humans.txt file (assuming I want to)

j-lea and others added 3 commits May 14, 2020 17:22
Tidy up wording around PWS/CF/TAS in upgrade and deploy instructions.

Co-authored-by: Jonathan Sharpe <[email protected]>
@j-lea j-lea force-pushed the feat-tanzu-deployment branch from 12d0a86 to 45b3022 Compare May 14, 2020 16:47
@butzopower
Copy link
Contributor

@textbook Anything left to do on this one? Think @j-lea has resolved all your change requests.

@textbook textbook self-requested a review May 22, 2020 10:14
@butzopower butzopower merged commit 4ac8aca into master May 22, 2020
@j-lea j-lea deleted the feat-tanzu-deployment branch June 4, 2020 09:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants