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
differentiate discovered resource names #28845
differentiate discovered resource names #28845
Changes from 1 commit
88d0c5c
56698b0
c3b3822
4d93110
09d6033
6af4bb9
3163807
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.
does this guarantee the name is unique? For e.g. an RDS instance and an RDS aroura cluster with same name in same region, same account? Similarly, Azure Redis vs Azure Redis enterprise.
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.
ah, thanks for pointing this out!
For Azure: Redis vs Redis Enterprise names must be unique because of the way Azure sets up DNS. I double checked that Azure enforces this just now.
Redis:
<name>.redis.cache.windows.net
SQL Server:
<name>.database.windows.net
Postgres:
<name.postgres.database.azure.com
MySQL:
<name>.mysql.database.azure.com
After experimenting some more in aws console, within a region database instance name must be unique amongst other instances (regardless of whether mysql or postgres), and Aurora cluster name must be unique amongst clusters (regardless of whether mysql or postgres). Since we group these under the single matcher type "rds", it won't be guaranteed to be unique :( I'll have to figure out some way to handle this
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 believe Redis enterprise uses a different suffix:
teleport/api/utils/azure/endpoints.go
Lines 123 to 130 in 2b15263
But regardless, we may have a problem when multiple fetchers share a matcher.
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.
@greedy52 coming back to this:
We are already renaming Aurora cluster dbs with a suffix:
-custom
, or-reader
, but we use the aurora cluster identifier as the first part of the name, not the individual instances' names.Therefore, I think we just need to distinguish between cluster dbs and instance dbs to get (most likely) unique naming for RDS/Aurora dbs.
rds
orrds-aurora
.For Redis, I tested the naming incorrectly in Azure when I tried, you're right that the names can overlap:
redis
orredis-enterprise
The others are not an issue due to naming uniqueness rules in Azure. Even SQL server vs managed SQL instance.
commit: 09d6033
and 3163807