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

Add JSON manifest for APIcast policy #601

Merged
merged 2 commits into from
Feb 19, 2018
Merged

Add JSON manifest for APIcast policy #601

merged 2 commits into from
Feb 19, 2018

Conversation

davidor
Copy link
Contributor

@davidor davidor commented Feb 16, 2018

Without a manifest, it will not show up in the policies endpoint.

@davidor davidor requested a review from mikz February 16, 2018 13:57
"$schema": "http://apicast.io/policy-v1/schema#manifest#",
"name": "Apicast policy",
"description": "Main functionality of APIcast.",
"version": "0.1",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be tricky @mikz .

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can have therebuiltin. The loaded already expects that for all builtin policies.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about that. It's not a problem for now, but what if in the next release we introduce a new config param for this policy? We'd need to somehow distinguish the 2 versions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean it seriously needs to be builtin because those have different load path. It will not work at all with normal version string unless we move all policies to different folders.

I think it is fine because they are not released separately. We will have to maintain backwards compatibility.

Why we would need to distinguish two versions ? There is going to be just one version of APIcast policy. We could add some extra property to the policy API to show version of APIcast itself.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean it seriously needs to be builtin because those have different load path. It will not work at all with normal version string unless we move all policies to different folders.

I think it is fine because they are not released separately. We will have to maintain backwards compatibility.

Why we would need to distinguish two versions ? There is going to be just one version of APIcast policy. We could add some extra property to the policy API to show version of APIcast itself.

Without a manifest, it will not show up in the policies endpoint.
@davidor davidor force-pushed the apicast-policy-schema branch from 4ea2607 to 7d9bf80 Compare February 16, 2018 13:59
@mikz mikz merged commit 5936d21 into master Feb 19, 2018
@davidor davidor deleted the apicast-policy-schema branch February 19, 2018 12:59
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

Successfully merging this pull request may close these issues.

2 participants