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

[v17] Fix discover reporting for static matchers #48424

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

marcoandredinis
Copy link
Contributor

Backport #48156 to branch/v17

Discovery Service now reports the status of the auto enrollment flows
when the matchers come from a DiscoveryConfig resource.

For static matchers, those in
`teleport.yaml/discovery_service.<cloud>.<matcher>` there's no status to
write to.
@marcoandredinis marcoandredinis added the no-changelog Indicates that a PR does not require a changelog entry label Nov 5, 2024
@marcoandredinis marcoandredinis marked this pull request as ready for review November 5, 2024 08:35
@github-actions github-actions bot requested review from kopiczko and tigrato November 5, 2024 08:36
@@ -45,6 +45,12 @@ import (
// - AWS Sync (TAG) status
// - AWS EC2 Auto Discover status
func (s *Server) updateDiscoveryConfigStatus(discoveryConfigName string) {
// Static configurations (ie those in `teleport.yaml/discovery_config.<cloud>.matchers`) do not have a DiscoveryConfig resource.
Copy link
Contributor

Choose a reason for hiding this comment

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

I forgot to ask in the original PR: isn't that teleport.yaml/discovery_service?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice catch 🙏
Yes, it should be.
I'll create another PR for the fix because we already merged it in master

@marcoandredinis marcoandredinis added this pull request to the merge queue Nov 5, 2024
Merged via the queue into branch/v17 with commit 34549d7 Nov 5, 2024
45 checks passed
@marcoandredinis marcoandredinis deleted the bot/backport-48156-branch/v17 branch November 5, 2024 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport discovery no-changelog Indicates that a PR does not require a changelog entry size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants