Add policy template for Compose deployments #8090
Open
Conversation
This file contains 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
buchi
force-pushed
the
compose-policy-template
branch
2 times, most recently
from
db90050 to
808f3e9
Compare
buchi
force-pushed
the
compose-policy-template
branch
3 times, most recently
from
3dce96b to
5af42c8
Compare
buchi
force-pushed
the
compose-policy-template
branch
from
5af42c8 to
0b2a958
Compare
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.
Extends the policy generator to allow creating policies for Docker Compose deployments.
Instructions for creating new deployments:
https://4teamwork.atlassian.net/wiki/spaces/4TEAM/pages/2045607937/Neues+Gever+Teamraum+Deployment+mit+Docker+Compose
The Compose files are split into multiple files:
compose-deployment.yaml(Services required for each Deployment)compose-geverui.yaml(Frontend)compose-ianus.yaml(Portal)compose-<server>-<num>-<name>.yaml(Specific Deployment)This allows easier customization without modifying the base yaml files.
Configuration settings are stored in
compose-<server>-<num>-<name>.envand customizations should be made preferably incompose-<server>-<num>-<name>.yaml.Checklist
Everything has to be done/checked. Checked but not present means the author deemed it unnecessary.