mirror of
https://github.com/kairos-io/kcrypt.git
synced 2025-04-27 11:21:45 +00:00
🌱 Remove challenger traces from here
The challenger has no business logic in here, and kcrypt should just read what it needs. This goes in parallel with https://github.com/kairos-io/kcrypt-challenger/pull/10 Not blocking each other. Signed-off-by: mudler <mudler@c3os.io>
This commit is contained in:
parent
27183fbce7
commit
71506ff020
@ -25,7 +25,6 @@ var MappingsFile = "/oem/91-kcrypt-mappings.yaml"
|
||||
|
||||
type Config struct {
|
||||
Kcrypt struct {
|
||||
Server string `yaml:"challenger_server,omitempty"`
|
||||
UUIDLabelMappings map[string]string `yaml:"uuid_label_mappings,omitempty"`
|
||||
}
|
||||
}
|
||||
|
@ -27,7 +27,6 @@ var _ = Describe("Config", func() {
|
||||
It("returns empty Config", func() {
|
||||
c, err := configpkg.GetConfiguration([]string{tmpDir})
|
||||
Expect(err).ToNot(HaveOccurred())
|
||||
Expect(c.Kcrypt.Server).To(BeEmpty())
|
||||
Expect(c.Kcrypt.UUIDLabelMappings).To(BeEmpty())
|
||||
})
|
||||
})
|
||||
@ -40,8 +39,6 @@ var _ = Describe("Config", func() {
|
||||
Expect(err).ToNot(HaveOccurred())
|
||||
data := []byte(`#cloud-config
|
||||
kcrypt:
|
||||
challenger_server: http://test.org:8082
|
||||
|
||||
uuid_label_mappings:
|
||||
COS_PERSISTENT: some_uuid_here
|
||||
`)
|
||||
@ -52,7 +49,6 @@ kcrypt:
|
||||
It("returns the Config", func() {
|
||||
c, err := configpkg.GetConfiguration([]string{tmpDir})
|
||||
Expect(err).ToNot(HaveOccurred())
|
||||
Expect(c.Kcrypt.Server).To(Equal("http://test.org:8082"))
|
||||
Expect(c.Kcrypt.UUIDLabelMappings["COS_PERSISTENT"]).To(Equal("some_uuid_here"))
|
||||
})
|
||||
})
|
||||
@ -84,7 +80,6 @@ kcrypt:
|
||||
It("returns the merged Config", func() {
|
||||
c, err := configpkg.GetConfiguration([]string{tmpDir})
|
||||
Expect(err).ToNot(HaveOccurred())
|
||||
Expect(c.Kcrypt.Server).To(Equal("http://test.org:8082"))
|
||||
Expect(c.Kcrypt.UUIDLabelMappings["COS_PERSISTENT"]).To(Equal("some_uuid_here"))
|
||||
})
|
||||
})
|
||||
|
Loading…
Reference in New Issue
Block a user