Tagged #hcl.
4 entries.
0 entries
week 1
week 1
0 entries
week 2
week 2
0 entries
week 3
week 3
0 entries
week 4
week 4
0 entries
week 5
week 5
0 entries
week 6
week 6
0 entries
week 7
week 7
0 entries
week 8
week 8
0 entries
week 9
week 9
0 entries
week 10
week 10
0 entries
week 11
week 11
0 entries
week 12
week 12
0 entries
week 13
week 13
0 entries
week 14
week 14
0 entries
week 15
week 15
0 entries
week 16
week 16
0 entries
week 17
week 17
0 entries
week 18
week 18
0 entries
week 19
week 19
0 entries
week 20
week 20
0 entries
week 21
week 21
0 entries
week 22
week 22
0 entries
week 23
week 23
0 entries
week 24
week 24
0 entries
week 25
week 25
0 entries
week 26
week 26
0 entries
week 27
week 27
0 entries
week 28
week 28
0 entries
week 29
week 29
0 entries
week 30
week 30
0 entries
week 31
week 31
0 entries
week 32
week 32
0 entries
week 33
week 33
0 entries
week 34
week 34
0 entries
week 35
week 35
0 entries
week 36
week 36
0 entries
week 37
week 37
1 entry
week 38
week 38
1 entry
week 39
week 39
1 entry
week 40
week 40
0 entries
week 41
week 41
0 entries
week 42
week 42
0 entries
week 43
week 43
0 entries
week 44
week 44
0 entries
week 45
week 45
0 entries
week 46
week 46
0 entries
week 47
week 47
1 entry
week 48
week 48
0 entries
week 49
week 49
0 entries
week 50
week 50
0 entries
week 51
week 51
0 entries
week 52
week 52
4 entries over 52 weeks of #hcl activity. Less More
Writing 3 posts
I Added Variable Block Support To Glazier
Why I Built Glazier
Bits 1 bit
Welp. I’ve convinced myself that Glazier needs Terraform-style variable declaration blocks to validate --var flags. I’m doing it and I will not be stopped. I’m thinking something as simple as the following session block-adjecent top-level spec:
HCL
variable "name" {
description = optional(string)
type = required(string | bool | number)
default = optional(type)
}Time to do what I do best: make things more complicated than they have any right to be.