Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 Authorization Rules for Client VPN #13950
Add Authorization Rules for Client VPN #13950
Changes from 48 commits
d8912bc
bbd7315
a97816b
ef5cba6
598d1cb
6638498
7995ce7
91e12b9
d0c9bbf
20f36e2
f7fa8f4
6cc4c31
5132423
88362fb
299594d
69207fe
baaedf8
d73e537
cac47ca
63f6b94
85d5e03
0fede62
8300857
540f123
9f7c429
3c41148
47b626d
a617731
b06cac4
c3e9794
fb0571d
2256f43
36185b3
af65152
17426db
706c2d2
ebc3e37
923ed2f
aaf82b7
9c04ab5
1b589c4
269186a
d85342a
a76229c
20569d6
bf963ee
bb1f70a
3858262
0a56fc8
4403fca
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the plan be to always separate
const
declarations in these files based on some criteria?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was following the model of a separate
const
block for each resource type as well as keeping them together with the correspondingStatus
functionThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely not something for this PR, but wonder if we should change these to per "resource" files then like
status_ClientVpnEndpoint.go
-- something to noodle over in #12840!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we'll need to globally decide whether errors like these should be handled in these service packages or downstream in the resource implementations so they can decide what to do with them. For example, this swallows available request ID information from the SDK unless debug logging is enabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, we need to handle at least some of the errors here, or else the calling
WaitForState()
will error out instead of returning cleanlyThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the real difference is that if/when this code is generated, it then needs an additional layer of knowledge of errors rather than just how to handle the API structures. Not a big deal in the short term, but something to consider for longer term.