veenj
/
cinit
1
0
Fork 0
Code Issues 3 Pull Requests Projects Releases Wiki Activity

Option to ignore symlinks #40

New Issue
Open
opened 2020-03-14 09:39:24 +01:00 by veenj · 0 comments
veenj commented 2020-03-14 09:39:24 +01:00 (Migrated from gitlab.com)
Copy Link

When using cinit with a configuration directory where all recursively included files are sourced, there should be a choice whether symlinks should be followed.

This is very useful inside Kubernetes where config files can be dynamically mounted into the cinit directory. However Kubernetes uses symlinks for this which makes programs appear twice in the config and therefore cinit fails to start up.

When using `cinit` with a configuration directory where all recursively included files are sourced, there should be a choice whether symlinks should be followed. This is very useful inside Kubernetes where config files can be dynamically mounted into the cinit directory. However Kubernetes uses symlinks for this which makes programs appear twice in the config and therefore cinit fails to start up.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
stable
issue-50
1.6.3
1.6.2
1.6.1
1.6.0
1.5.2
1.5.1
1.5.0
1.4.2
1.4.1
1.4.0
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.2
1.1.1
1.0.1
1.0.0
0.1.0
Labels
Clear labels   
Bug

   
Feature

   
QA

   
Testing
No Label
Bug
Feature
QA
Testing
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: veenj/cinit#40
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?