@flow-as-code/tf 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 The flow-as-code Authors
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,67 @@
1
+ # @flow-as-code/tf
2
+
3
+ ```
4
+ npm i @flow-as-code/tf
5
+ ```
6
+
7
+ Apache-2.0, Node 22.12 or newer.
8
+
9
+ Implements docs/03-tf-emitter.md. Deterministic HCL emission, `terraform validate`-clean when the address map is complete, loud TODO placeholders when it is not. Never emits literal ARNs, provider blocks, or backend config.
10
+
11
+ One-way in v1: FlowDoc in, HCL out. Reading HCL back into FlowDoc needs HCL evaluation and is deferred to the provider era.
12
+
13
+ ## Use
14
+
15
+ ```ts
16
+ import { emitTf, writeTf } from "@flow-as-code/tf";
17
+
18
+ const { files } = emitTf([doc], {
19
+ addressMap: { "queue:front-desk": "aws_connect_queue.front_desk.arn" },
20
+ });
21
+
22
+ writeTf([doc], "infra/flows", { addressMap });
23
+ ```
24
+
25
+ `emitTf` is pure: documents in, a relative path to content map out, sorted by path and byte-identical across runs. `writeTf` is the filesystem wrapper; it creates directories, overwrites the files it emits, and touches nothing else in the target directory.
26
+
27
+ `@flow-as-code/tf/emit` is the same emitter without the filesystem half. The package index re-exports `writeTf`, which imports `node:fs`, so a browser bundle (`@flow-as-code/studio`'s Terraform export) imports the subpath instead.
28
+
29
+ ## Output
30
+
31
+ | File | What it holds |
32
+ | ------------------------- | ------------------------------------------------------------------------------------------------------------- |
33
+ | `flows/<name>.flow.tftpl` | Deployable Flow language JSON, each reference replaced by a `templatefile` interpolation |
34
+ | `flows.tf` | `aws_connect_contact_flow` / `aws_connect_contact_flow_module`, plus awscc module version and alias resources |
35
+ | `flow_refs.tf` | `locals` holding the terraform address behind every reference |
36
+ | `variables.tf` | The Connect instance id variable, unless `instanceIdExpression` supplies one |
37
+ | `versions.tf.example` | Required providers and versions, as an example; not loaded by either tool |
38
+
39
+ Provider configuration, credentials, and backend configuration are yours. The emitter writes none of them, by rule.
40
+
41
+ ## References
42
+
43
+ Every `${cdref:type:name}` token becomes a template variable named `<type>_<name>_arn`, hyphens as underscores, with a module alias folded in: `queue_front_desk_arn`, `module_survey_prod_arn`. Addresses come from three places, in this order:
44
+
45
+ 1. **The document set itself.** A `${cdref:module:x@prod}` whose module `x` is emitted here resolves to `awscc_connect_contact_flow_module_alias.x_prod.contact_flow_module_alias_arn`; a `${cdref:flow:y}` whose flow `y` is emitted here resolves to that flow. An address map entry for one of these is ignored, and the emitted file says so on the line above.
46
+ 2. **The address map.** Keys are a token (`${cdref:queue:front-desk}`), the token body (`queue:front-desk`, `module:survey@prod`), or the variable name (`queue_front_desk_arn`). Values are HCL address expressions. A literal ARN is refused, as is anything that would comment out or overrun its line. Entries matching no reference in the set are ignored, so one shared map can serve several flow sets.
47
+ 3. **Nothing.** The entry becomes `TODO_MISSING_ADDRESS_<type>_<name>` with a `# TODO` naming the reference. That is an undeclared reference, so `terraform validate` and `tofu validate` fail loudly rather than an apply writing a broken flow.
48
+
49
+ Addresses of resources the set emits itself live in a per-document local (`merge(local.flow_refs, { ... })`) rather than in the shared map. Putting them in the shared map makes the map depend on the resources rendered from it, and both tools report that as a dependency cycle. Two flows that reference each other are still a cycle, because it is one.
50
+
51
+ ## Escaping
52
+
53
+ The `.tftpl` body is JSON containing caller text, and caller text legitimately contains `${` and `%{`, the two sequences HCL reads as template introducers. Every one of them is escaped (`$${`, `%%{`) and only the emitter's own reference interpolations are left live. The substitution runs through unique sentinels chosen so they cannot collide with the document, so text that looks like a sentinel is caller text and stays caller text. `conformance/emit-tf/hostile-text` holds the fixture, and the gated tests render it with a real `tofu` and compare against a reference implementation of the template grammar.
54
+
55
+ ## Versions and aliases
56
+
57
+ Flow versioning is not available: `CreateContactFlowVersion` "only supports creating versions for flows of type Campaign" ([API reference](https://docs.aws.amazon.com/connect/latest/APIReference/API_CreateContactFlowVersion.html)). Flows update their content in place. Modules get `awscc_connect_contact_flow_module_version` and `awscc_connect_contact_flow_module_alias`, which is how a caller pins the module content it invokes. A version snapshots content at create time, so a module content change needs the version resource replaced for aliases to serve it.
58
+
59
+ ## Tests
60
+
61
+ `npm test` runs the goldens in `conformance/emit-tf` and the unit tests. The tests that run a real `tofu init`, `tofu validate`, `tofu fmt`, and `tofu console` need the network and a few minutes on a cold provider cache, so they are gated behind `RUN_TOFU_VALIDATE=1`:
62
+
63
+ ```sh
64
+ RUN_TOFU_VALIDATE=1 npx vitest run --project @flow-as-code/tf
65
+ ```
66
+
67
+ CI runs them in the `emit-tf` job, and an ungated test asserts that the job still sets the variable. Regenerate goldens deliberately with `UPDATE_GOLDENS=1` and read the diff.
package/dist/emit.d.ts ADDED
@@ -0,0 +1,45 @@
1
+ import { type FlowDoc } from "@flow-as-code/core";
2
+ /**
3
+ * The oldest core version the emitted configuration promises to work on, per
4
+ * docs/03-tf-emitter.md ("emit nothing Terraform 1.8+/OpenTofu 1.7+ do not both
5
+ * support"). It lands in every `versions.tf.example` as `required_version`, and
6
+ * the emit-tf CI job is asserted to run the gated suite against it, so the
7
+ * promise and the thing that checks the promise cannot drift apart.
8
+ */
9
+ export declare const CORE_VERSION_FLOOR = "1.7.0";
10
+ /** Emission refused. Every problem found is listed, not just the first. */
11
+ export declare class EmitTfError extends Error {
12
+ readonly problems: readonly string[];
13
+ constructor(problems: readonly string[]);
14
+ }
15
+ export interface EmitTfOptions {
16
+ /**
17
+ * Reference to terraform address expression, for references this emitter
18
+ * cannot resolve from the document set itself. A key is a token
19
+ * (`${cdref:queue:front-desk}`), the token body (`queue:front-desk`,
20
+ * `module:survey@prod`), or the generated variable name
21
+ * (`queue_front_desk_arn`); the three are tried in that order. Values are HCL
22
+ * expressions such as `aws_connect_queue.front_desk.arn`, never literal ARNs.
23
+ * Entries matching no reference in the set are ignored.
24
+ */
25
+ addressMap?: Record<string, string>;
26
+ /**
27
+ * Expression for the `instance_id` argument. Defaults to
28
+ * `var.connect_instance_id`, in which case variables.tf declaring that
29
+ * variable is emitted too. Pass something else (`aws_connect_instance.main.id`)
30
+ * to wire the flows into an instance you already manage; no variables.tf is
31
+ * emitted then.
32
+ */
33
+ instanceIdExpression?: string;
34
+ }
35
+ export interface EmitTfResult {
36
+ /** Relative POSIX path to file content, insertion-ordered by sorted path. */
37
+ files: Record<string, string>;
38
+ }
39
+ /**
40
+ * Emits a Terraform/OpenTofu configuration for a set of FlowDocs. Pure and
41
+ * deterministic: the same documents and options produce byte-identical files,
42
+ * and paths come back sorted.
43
+ */
44
+ export declare function emitTf(docs: readonly FlowDoc[], options?: EmitTfOptions): EmitTfResult;
45
+ //# sourceMappingURL=emit.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"emit.d.ts","sourceRoot":"","sources":["../src/emit.ts"],"names":[],"mappings":"AAmBA,OAAO,EACL,KAAK,OAAO,EAMb,MAAM,oBAAoB,CAAC;AAI5B;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB,UAAU,CAAC;AAE1C,2EAA2E;AAC3E,qBAAa,WAAY,SAAQ,KAAK;IACpC,QAAQ,CAAC,QAAQ,EAAE,SAAS,MAAM,EAAE,CAAC;gBAEzB,QAAQ,EAAE,SAAS,MAAM,EAAE;CAKxC;AAED,MAAM,WAAW,aAAa;IAC5B;;;;;;;;OAQG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACpC;;;;;;OAMG;IACH,oBAAoB,CAAC,EAAE,MAAM,CAAC;CAC/B;AAED,MAAM,WAAW,YAAY;IAC3B,6EAA6E;IAC7E,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CAC/B;AAsZD;;;;GAIG;AACH,wBAAgB,MAAM,CAAC,IAAI,EAAE,SAAS,OAAO,EAAE,EAAE,OAAO,GAAE,aAAkB,GAAG,YAAY,CA8C1F"}