adding init #501
Merged
adding init #501
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
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.
Adds an "init" step to various parts of the project:
manifests/apps/kustomization.yamlfile, a new resource./devcontaineris included.terraform/cloud-init/fortiweb.conffile, the "allowaccess" configuration for "port2" now includeshttpsin addition toping.terraform/spoke-k8s_cluster.tffile, a new trigger is added to thenull_resource"kube_config" to ensure it always runs. Additionally, the secret created in the local-exec provisioner is now namedfortiweb-logininstead offwb-login.These changes aim to enhance the initialization process and improve the overall setup and configuration of the project.