-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore(docs): Add guidance about deprecated deployment methods and intended support #1276
Chore(docs): Add guidance about deprecated deployment methods and intended support #1276
Conversation
Will add a doc fix for #1239 as well because it touches on similar issues |
…/eeaton/terraform-example-foundation into readme-update-deployment-options
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor fix.
LGTM
accept suggested changes Co-authored-by: Daniel Andrade <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already reviewed by @daniel-cit
Though this blueprint can help accelerate your foundation design and build, we assume that you have the engineering skills and teams to deploy and customize your own foundation based on your own requirements. | ||
|
||
We will support: | ||
- Code is semantically valid, pinned to known good versions, and passes terraform validate and lint checks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: proper noun?
- Code is semantically valid, pinned to known good versions, and passes terraform validate and lint checks | |
- Code is semantically valid, pinned to known good versions, and passes Terraform validate and lint checks |
Though this blueprint can help accelerate your foundation design and build, we assume that you have the engineering skills and teams to deploy and customize your own foundation based on your own requirements. | ||
|
||
We will support: | ||
- Code is semantically valid, pinned to known good versions, and passes terraform validate and lint checks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Code is semantically valid, pinned to known good versions, and passes terraform validate and lint checks | |
- Code is semantically valid, pinned to known good versions, and passes Terraform validate and lint checks |
Warnings about jenkins, CSR for new organizations.
I raised this issue in #1275 1275. Quick fix until we can properly address this in #1249