feat: set puppet uid/gid in container build #125
Merged
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.
I want to connect an EFS to the ECS Service for the ca mountpoint and by creating an access point and setting ownership and permissions, we can have EFS create a directory for us, and make sure we always use the same UID/GID when accessing files. That makes re-deploys of the stack possible without user id issues…
For this to be possible we must be certain the UID/GID are static.
Just setting these at build time makes this possible.