Skip to content

bazel: Add json_data and writers#18086

Merged
htuch merged 2 commits intoenvoyproxy:mainfrom
phlax:bazel-json-data
Sep 15, 2021
Merged

bazel: Add json_data and writers#18086
htuch merged 2 commits intoenvoyproxy:mainfrom
phlax:bazel-json-data

Conversation

@phlax
Copy link
Copy Markdown
Member

@phlax phlax commented Sep 11, 2021

Signed-off-by: Ryan Northey ryan@synca.io

Commit Message: bazel: Add json_data and providers
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

@phlax phlax force-pushed the bazel-json-data branch 3 times, most recently from 9627f43 to 9e974eb Compare September 11, 2021 17:29
Signed-off-by: Ryan Northey <ryan@synca.io>
]
for d in api_dirs:
ctx.symlink(ctx.path(ctx.attr.envoy_root).dirname.get_child(ctx.attr.reldir).get_child(d), d)
ctx.symlink(ctx.path(ctx.attr.envoy_root).dirname.get_child("bazel").get_child("utils.bzl"), "utils.bzl")
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

ive tried a few different ways to make the json_data macro available in the api part of the repo

not sure the best way

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Possibly the cleanest way is to put the json_data macro inside api/bazel. That makes the dependency chain simpler.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

not sure why i didnt think of that - ill move it

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

...in a follow up...

@phlax phlax changed the title bazel: Add json_data and providers bazel: Add json_data and writers Sep 12, 2021
htuch
htuch previously approved these changes Sep 13, 2021
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

Nice!

]
for d in api_dirs:
ctx.symlink(ctx.path(ctx.attr.envoy_root).dirname.get_child(ctx.attr.reldir).get_child(d), d)
ctx.symlink(ctx.path(ctx.attr.envoy_root).dirname.get_child("bazel").get_child("utils.bzl"), "utils.bzl")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Possibly the cleanest way is to put the json_data macro inside api/bazel. That makes the dependency chain simpler.

Signed-off-by: Ryan Northey <ryan@synca.io>
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@htuch htuch merged commit c74b352 into envoyproxy:main Sep 15, 2021
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