diff --git a/README.md b/README.md index b33d5e4..f1ba60e 100644 --- a/README.md +++ b/README.md @@ -102,7 +102,7 @@ output "instance-ip" { As you can see, there are 4 [terraform] resources declared up above and their relationships are as follow. - + - `instance-ip` depends on `my-ec2-instance` - `my-ec2-instance` depends on `my-subnet` @@ -163,7 +163,7 @@ In [cdktf], every resource is a class instance. Thoese are pretty straight forwa However unlike `hcl`, it is a sequencial language. You cannot create instance refering to another one that is not defined yet. - + When you attempt to declare `subnet` before `vpc`, it'll say "Hey, you cannot use `vpc` before it's been initialized!" diff --git a/docs/classes/TerraformInjectorStack.html b/docs/classes/TerraformInjectorStack.html index da6a4e8..b2465d9 100644 --- a/docs/classes/TerraformInjectorStack.html +++ b/docs/classes/TerraformInjectorStack.html @@ -1,7 +1,7 @@
Set backend of the injector. You cannot provide multiple backend elements to the injector and only one backend could be provided for one stack each.
Optional description string.
-Commit dependency injection for all the elements below the scope level.
-Provide an element to the injector.
Stack class extends TerraformStack
and implementing TerraformInjectorAsync.
Set backend of the injector. You cannot provide multiple backend elements to the injector and only one backend could be provided for one stack each.
Optional description string.
-Commit dependency injection for all the elements below the scope level.
-Provide an element to the injector.
As you can see, there are 4 terraform resources declared up above and their relationships are as follow.
- +instance-ip
depends on my-ec2-instance
In cdktf, every resource is a class instance. Thoese are pretty straight forward. Constructing resources using new
keyword, passing id string and its config, you can build real world infrastructure.
However unlike hcl
, it is a sequencial language. You cannot create instance refering to another one that is not defined yet.
When you attempt to declare subnet
before vpc
, it'll say "Hey, you cannot use vpc
before it's been initialized!"
And that's where the cdktf-injector
comes in.
You can provide any elements inheriting TerraformElement
with provide
method.
And there is a special backend
method only for providing an TerraformBackend
element.
You can later inject all the dependencies below the scope level of the instance by using inject
method.
Set backend of the injector. You cannot provide multiple backend elements to the injector and only one backend could be provided for one stack each.
Optional description string.
-Provide an element to the injector.
You can provide any elements inheriting TerraformElement
with provide
method.
And there is a special backend
method only for providing an TerraformBackend
element.
You can later inject all the dependencies below the scope level of the instance by using inject
method.
Set backend of the injector. You cannot provide multiple backend elements to the injector and only one backend could be provided for one stack each.
Optional description string.
-Commit dependency injection for all the elements below the scope level.
-Provide an element to the injector.
You can provide any elements inheriting TerraformElement
with provide
method.
And there is a special backend
method only for providing an TerraformBackend
element.
You can later inject all the dependencies below the scope level of the instance by using inject
method.
Set backend of the injector. You cannot provide multiple backend elements to the injector and only one backend could be provided for one stack each.
Optional description string.
-Commit dependency injection for all the elements below the scope level.
-Provide an element to the injector.
Injectable terraform element container. You cannot instantiate directly, only by
yourInjector.provide
or yourInjector.backend
(for backend only).
Get terraform element.
Get shared object.
Configuration callbak for TerraformOutput
class.
Add after dependencies injected callback
. Callback will run after dependency injection process is completed.
You can add multiple callbacks, then they will be executed in sequence.
Action block to execute after di process
-Add after init callback
. Callbacks will run right after this element is initialized.
You can add multiple callbacks, then they will be executed in sequence.
Injectable terraform element container. You cannot instantiate directly, only by
yourInjector.provide
or yourInjector.backend
(for backend only).
Get terraform element.
Get shared object.
Configuration callbak for TerraformOutput
class.
Add after dependencies injected callback
. Callback will run after dependency injection process is completed.
You can add multiple callbacks, then they will be executed in sequence.
Action block to execute after di process
-Add after init callback
. Callbacks will run right after this element is initialized.
You can add multiple callbacks, then they will be executed in sequence.
Constant object for creating TerraformInjector or TerraformInjectorAsync instance.
You can use only one of scopesOn
or scopesOnAsync
function for one Construct instance, not both.
Stack class extends
TerraformStack
and implementing TerraformInjector.https://www.terraform.io/cdktf/concepts/stacks
-