You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support to output GUID for instance / firewall for bucket / kms encryption for bucket (#14)
* Add guid output for instance and Firewall for bucket
* update readme files
* Add encrypton key crn to storage bucket
* Change name of variable for encryption
* Update examples with changes
Co-authored-by: Adam Geiger <ageiger@us.ibm.com>
Copy file name to clipboardExpand all lines: examples/bucket/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,10 +97,11 @@ module "cos_bucket" {
97
97
| logdna\_crn | instance crn of logdna that will receive object event data | string | n/a | no |
98
98
| read\_data\_events | If set to true, all object write events will be sent to Activity Tracke/logdna | bool |`true`| no |
99
99
| write\_data\_events | If set to true, all object write events will be sent to Activity Tracke/logdna | bool |`true`| no |
100
-
100
+
| allowed_ip | A list of IPs you want to allow access to your bucket. | list | n/a | no |
101
+
| kms_key_crn | The CRN of the root key that you want to use to encrypt data | string | n/a | no |
101
102
102
103
## NOTE:
103
104
104
105
* If we want to make use of a particular version of module, then set the argument "version" to respective module version.
105
106
106
-
* To attach a key to cos instance, enbale it by setting `bind_resource_key` argument to true (which is by default false). And set the `resource_key_name` and `role` parameters accordingly (which are by deafult empty) in variables.tf file.
107
+
* To attach a key to cos instance, enbale it by setting `bind_resource_key` argument to true (which is by default false). And set the `resource_key_name` and `role` parameters accordingly (which are by deafult empty) in variables.tf file.
Copy file name to clipboardExpand all lines: examples/configure-bucket/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,12 +91,13 @@ module "cos_bucket" {
91
91
| force\_delete | COS buckets need to be empty before they can be deleted | bool |`true`| no |
92
92
| read\_data\_events | If set to true, all object write events will be sent to Activity Tracke/logdna | bool |`true`| no |
93
93
| write\_data\_events | If set to true, all object write events will be sent to Activity Tracke/logdna | bool |`true`| no |
94
-
94
+
| allowed_ip | A list of IPs you want to allow access to your bucket. | list | n/a | no |
95
+
| kms_key_crn | The CRN of the root key that you want to use to encrypt data | string | n/a | no |
95
96
96
97
## NOTE :
97
98
98
99
* If we want to make use of a particular version of module, then set the argument "version" to respective module version.
99
100
100
101
* Set the `archive_rule_enabled` argument to true only for regional cos bucket creation. For cross region and singleSite location set to false.
101
102
102
-
* To attach a key to cos instance, enbale it by setting `bind_resource_key` argument to true (which is by default false). And set the `resource_key_name` and `role` parameters accordingly (which are by deafult empty) in variables.tf file.
103
+
* To attach a key to cos instance, enbale it by setting `bind_resource_key` argument to true (which is by default false). And set the `resource_key_name` and `role` parameters accordingly (which are by deafult empty) in variables.tf file.
0 commit comments