-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Fix for ram shared avmc #45583
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
base: main
Are you sure you want to change the base?
Fix for ram shared avmc #45583
Conversation
|
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
74780da to
0be214d
Compare
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
No
Description
Autonomous VM cluster creation using ARN
There are some special account called RAM shared account for which AWS API doesn't accept ids of odb network and exadata infrastructure while creating vm cluster , only supports ARN.
Note : odb network and exadata infra are only resources that can be RAM shared.
This PR enables VM cluster to accept either combination of (odb network + exadata infra id) Or (odb network + exadata infra ARN)
References
https://docs.aws.amazon.com/odb/latest/UserGuide/sharing-resources-task.html
Output from Acceptance Testing