refactor(services): restructure services layer in root module #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
axel-ippon
changed the title
Removes default values from module variables to require explicit project names Standardizes resource tagging from tags_all to tags throughout services module Adds CloudFront provider configuration with us-east-1 region requirement Improves resource naming consistency by removing generic names like "example"
Eliminates the services layer infrastructure as part of moving service components to the root module.
axel-ippon
force-pushed
the
feature/290-move-service-layer-in-root-module
branch
from
0d58e85 to
2f9c438
Compare
sroulon-ippon
approved these changes
Dec 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Moves services infrastructure from layered architecture to a root module approach, consolidating configuration files and simplifying deployment structure.
Reference issues or tasks
291