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

provider/aws: ability to generate unique RDS identifier #5723

Merged
merged 1 commit into from
Mar 18, 2016

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Mar 18, 2016

Needed to truncate the identifier for SQL Server engines to keep it at
max 15 chars per the docs. Not a full UUID going into it, but should be
"unique enough" to not matter in practice.

Modified the basic test to use the generated value. Other tests are
still working w/ explicitly specified identifiers.

@stack72
Copy link
Contributor

stack72 commented Mar 18, 2016

LGTM! Will be a nice addition when needing to write tests going forward :)

@catsby
Copy link
Contributor

catsby commented Mar 18, 2016

👍

Needed to truncate the identifier for SQL Server engines to keep it at
max 15 chars per the docs. Not a full UUID going into it, but should be
"unique enough" to not matter in practice.

Modified the basic test to use the generated value. Other tests are
still working w/ explicitly specified identifiers.
@phinze phinze force-pushed the phinze/rds-instance-generate-identifier branch from e179a71 to 4e5429a Compare March 18, 2016 21:07
phinze added a commit that referenced this pull request Mar 18, 2016
…identifier

provider/aws: ability to generate unique RDS identifier
@phinze phinze merged commit d60bf93 into master Mar 18, 2016
@phinze phinze deleted the phinze/rds-instance-generate-identifier branch March 18, 2016 21:16
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants