-
Notifications
You must be signed in to change notification settings - Fork 4k
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
NeptuneDatabase spins up RDS Aurora MySQL by default #807
Labels
bug
This issue is a bug.
Comments
Good diagnosis, thanks for the report 😊. Honestly, the Neptune module is an untested unsupported proof of concept. We might need to remove it. |
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
RomainMuller
added a commit
that referenced
this issue
Oct 4, 2018
The Neptune package that was provided so far was the result of a proof-of-concept that was made before the eventual Neptune API was made available. Replacing this with the generated L1 for Neptune, that would otherwise not have been available at all. Fixes #807
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
New user! This is all using TypeScript.
Tried to follow the Neptune example. Got an RDS cluster running Aurora instead:
I think that this happened because of line 123 here. Should read
engine: rds.DatabaseClusterEngine.Neptune,
if the DatabaseClusterEngine enum works the way I think it does.As a workaround, I tried creating the cluster as an RDS object like so:
This transpiled just fine. cdk diff showed that the old instances would be destroyed and new ones would be stood up, as expected, but CloudFormation bounced it during deployment with the following message:
I tried removing the masterUser block and also just removing the username and password fields in the block, but in both cases the code wouldn't transpile:
Theory: Neptune doesn't expect a username/password, but the CDK expects Neptune to expect a username/password.
The text was updated successfully, but these errors were encountered: