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

x component is in the x.tf or x-component/main.tf #31

Conversation

amazingandyyy
Copy link
Member

@amazingandyyy amazingandyyy commented Jun 24, 2024

Description

  • add shell script to ensure component is defined inside the correct component.tf file OR parent-component/main.tf

Changes

  • feat(hooks): check component is defined inside the correct component file

🚀 PR created with fotingo

@amazingandyyy amazingandyyy requested a review from a team as a code owner June 24, 2024 18:05
@amazingandyyy amazingandyyy force-pushed the f/cloud-113_standard_as_code_component_is_in_the_component_file branch from 156e11e to f1065fa Compare June 24, 2024 18:20
@amazingandyyy amazingandyyy force-pushed the f/cloud-113_standard_as_code_component_is_in_the_component_file branch 7 times, most recently from 8ac936f to b51470b Compare June 24, 2024 20:33
@gopkri24
Copy link
Contributor

Looks like it might be an outcome of RFC-288

@amazingandyyy
Copy link
Member Author

@gopkri24 might have some overlap, but this is codify our existing standard for domain infra

@amazingandyyy
Copy link
Member Author

amazingandyyy commented Jun 24, 2024

I think your result proposal should consider backward compatible to the existing standard or come back to change the logic in the hook

@amazingandyyy amazingandyyy requested a review from gopkri24 June 24, 2024 21:15
Copy link
Contributor

@greenkiwi greenkiwi left a 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?

@amazingandyyy
Copy link
Member Author

amazingandyyy commented Jun 24, 2024

@greenkiwi this script does allow component/main.tf case

@amazingandyyy amazingandyyy changed the title CLOUD-113: [Standard as Code] component is in the component file x component is in the x.tf or x-component/main.tf Jun 24, 2024
@amazingandyyy amazingandyyy requested a review from greenkiwi June 24, 2024 22:43
@amazingandyyy amazingandyyy force-pushed the f/cloud-113_standard_as_code_component_is_in_the_component_file branch 6 times, most recently from cac42ea to 5d316a0 Compare June 25, 2024 17:20
@amazingandyyy amazingandyyy requested review from tagoro9 and greenkiwi and removed request for greenkiwi July 2, 2024 16:50
@amazingandyyy amazingandyyy deleted the f/cloud-113_standard_as_code_component_is_in_the_component_file branch July 3, 2024 00:42
@amazingandyyy amazingandyyy restored the f/cloud-113_standard_as_code_component_is_in_the_component_file branch July 3, 2024 00:47
@amazingandyyy amazingandyyy reopened this Jul 3, 2024
@amazingandyyy amazingandyyy force-pushed the f/cloud-113_standard_as_code_component_is_in_the_component_file branch from 5d316a0 to 9c81fe9 Compare July 3, 2024 00:49
@amazingandyyy amazingandyyy force-pushed the f/cloud-113_standard_as_code_component_is_in_the_component_file branch from 9c81fe9 to 2722c12 Compare July 3, 2024 00:49
@amazingandyyy amazingandyyy deleted the f/cloud-113_standard_as_code_component_is_in_the_component_file branch July 3, 2024 00:49
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