Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: make deck's file compatible with Kong's config file #26

Closed
hbagdi opened this issue Jun 21, 2019 · 0 comments
Closed
Milestone

Comments

@hbagdi
Copy link
Member

hbagdi commented Jun 21, 2019

decK was designed keeping in mind compatibility with Kong's native declarative config file.

Currently, all that is needed to make the file compatible with Kong's declarative config file is to add the following line:

_format_version: "1.1"
@hbagdi hbagdi added this to the v0.5.0 milestone Jul 26, 2019
hbagdi added a commit that referenced this issue Jul 27, 2019
decK's output file is compatible with
Kong's config file for db-less deployments and DB import
introduced in Kong 1.1 except that it needs the following property in
the file:

```
_format_string: "1.1"
```

This commit adds that property so that the file generated by decK
can be used directly by Kong.

See #26
@hbagdi hbagdi closed this as completed Jul 27, 2019
rainest pushed a commit that referenced this issue Apr 21, 2021
rainest pushed a commit that referenced this issue Apr 21, 2021
decK's output file is compatible with
Kong's config file for db-less deployments and DB import
introduced in Kong 1.1 except that it needs the following property in
the file:

```
_format_string: "1.1"
```

This commit adds that property so that the file generated by decK
can be used directly by Kong.

See #26
AntoineJac pushed a commit that referenced this issue Jan 23, 2024
decK's output file is compatible with
Kong's config file for db-less deployments and DB import
introduced in Kong 1.1 except that it needs the following property in
the file:

```
_format_string: "1.1"
```

This commit adds that property so that the file generated by decK
can be used directly by Kong.

See #26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant