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
[teleport-update] Add enable command #47565
[teleport-update] Add enable command #47565
Changes from 19 commits
0eef6c8
3bdc3e7
21a0507
7c432a6
bab8e18
fedc914
37bc3cd
46fb8e0
bec25c3
f0c343a
2eab556
0aa4172
6e905d5
c1ecf82
3d27750
1378714
74f20f2
3e1586e
84a7a2a
4f1033d
1ce6bee
ca5169e
46c92f4
f97950e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
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.
It's the first time I see something like this. How exactly does it work? Is there some sort of conditional compilation built into our makefiles?
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 copied this from #47466. Both the
client
andagent
packages will use the same flag set fromlib/autoupdate
in an upcoming PR. The build flags should be set when compiled viateleport.e
. See the top of the file:@vapopov I'm noticing now that this flag is only used in
webassets_embed_ent.go
, and thewebassets
prefix is confusing in this non-web-asset context. Would it make sense to look into making this flag more generic?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.
yes, I previously mentioned about this one #46587 (comment) since we don't have proper build flag for ent
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.
Can we use the
modules
package for this instead of making new flags? This package can already tell you if the binary is OSS, Enterprise, FIPS, etc.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.
Maybe we open a separate PR that renames the build flag so that it can be used in a wider context?(race condition on the Github comments)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 don't think
modules.GetModules().IsEnterpriseBuild()
will work as-is forteleport-update
, since it doesn't have a separatetool/teleport-update
target in teleport.e that runsmodules.SetModules()
.That said, we actually want the edition of the agent download to come from the cluster via
/webapi/find
before this ships, so I'll just default it to false and add a TODO for now.@vapopov you should be able to
modules
fortsh
andtctl
, buttbot
may not work for the reason mentioned.