Skip to content
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

Merged

Conversation

eeaton
Copy link
Collaborator

@eeaton eeaton commented Jun 24, 2024

Warnings about jenkins, CSR for new organizations.

I raised this issue in #1275 1275. Quick fix until we can properly address this in #1249

@eeaton eeaton changed the title Chore: Add warnings about deprecated deployment methods Chore(docs): Add warnings about deprecated deployment methods Jun 24, 2024
@eeaton eeaton changed the title Chore(docs): Add warnings about deprecated deployment methods Chore(docs): Add guidance about deprecated deployment methods and intended support Jun 24, 2024
@eeaton
Copy link
Collaborator Author

eeaton commented Jun 24, 2024

Will add a doc fix for #1239 as well because it touches on similar issues

@eeaton eeaton enabled auto-merge (squash) June 24, 2024 09:56
@eeaton eeaton requested a review from daniel-cit June 24, 2024 12:17
Copy link
Contributor

@daniel-cit daniel-cit left a 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

README.md Outdated Show resolved Hide resolved
accept suggested changes

Co-authored-by: Daniel Andrade <[email protected]>
Copy link
Contributor

@apeabody apeabody left a 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
Copy link
Contributor

@apeabody apeabody Jun 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: proper noun?

Suggested change
- 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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

@eeaton eeaton merged commit 98a6b50 into terraform-google-modules:master Jun 24, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants