Proposal: Restructure AWS branch to align with Terraform best practices #140
jdbraun-db
started this conversation in
General
Replies: 3 comments
-
I think this makes perfect sense - it brings the AWS codebase into conformity with many Terraform conventions, and will assist in discoverability for users familiar with said conventions. In my opinion, ship it! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Agreed with Nathan, I think this makes sense. We'll focus on keeping Azure in line with this practice also. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey folks, after reviewing the repository, I wanted to propose a few changes to the AWS branch to better align with Terraform best practices and simplify the structure for users.
Proposed changes:
These changes would flatten the directory structure and create a simpler entry point to SRA. This is especially helpful for folks with a more traditional DevOps background, instead of a Databricks / data one.
While this is a fairly significant structural change, I don’t expect it to be too disruptive since the vast majority of users are using SRA as an entry point and we’re operating on a point-in-time best practices model.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions