-
Notifications
You must be signed in to change notification settings - Fork 0
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
x component is in the x.tf or x-component/main.tf #31
x component is in the x.tf or x-component/main.tf #31
Conversation
156e11e
to
f1065fa
Compare
8ac936f
to
b51470b
Compare
Looks like it might be an outcome of RFC-288 |
@gopkri24 might have some overlap, but this is codify our existing standard for domain infra |
I think your result proposal should consider backward compatible to the existing standard or come back to change the logic in the hook |
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.
@amazingandyyy This seems too aggressive.
Do we really want this?
I could easily see a place where you had created a component in a directory
/systems/some-system/this-component/
And it would be really natural and probably right to put the component in the main.tf
directory.
Maybe the check is ok in main, if in directory with component in it
? Or maybe full path to file needs to have component
in it?
@greenkiwi this script does allow |
cac42ea
to
5d316a0
Compare
5d316a0
to
9c81fe9
Compare
9c81fe9
to
2722c12
Compare
Description
component.tf
file ORparent-component/main.tf
Changes
🚀 PR created with fotingo