-
Notifications
You must be signed in to change notification settings - Fork 39
doc: Import support documentation and considerations #1305
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
Conversation
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.
All the resources we have support import because all resources have full CRUD support.
cfn-resources/README.md
Outdated
|
|
||
| 1. **DeletionPolicy Attribute**: Your resource template must include the [DeletionPolicy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) attribute in order to specify what happens to the resource when it is removed from the stack. | ||
|
|
||
| 2. **UPDATE Operation Required**: The import operation executes the UPDATE operation behind the scenes. Therefore, UPDATE functionality must be properly implemented for the resource type to support import. |
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.
thank you, the nit I have is that this should be linked to some AWS documentation or at least specify that it's how AWS CFN works
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.
Added some link explaining the import flow where they explain the change set being created and when it is executed
marcosuma
left a comment
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.
overall LGTM, just a minor feedback on adding a link
|
@oarbusi let's get a docs team review on this |
|
|
||
| ## Resource Import Operations | ||
|
|
||
| All MongoDB Atlas AWS CloudFormation resources support the import operation, allowing you to bring existing Atlas resources under CloudFormation management. When importing resources, please consider the following: |
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.
Our main README file calls out import as a limitation: https://github.com/mongodb/mongodbatlas-cloudformation-resources?tab=readme-ov-file#limitations
We can definitely adjust that content, also thinking if we do a brief mention of import functionality in the main readme and reference here for more visibility.
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.
Addressed, thanks!
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.
@oarbusi should we also mention that Import is available in the main readme and link to here, like Agustin suggested?
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.
done in a514b82
Co-authored-by: lmkerbey-mdb <[email protected]>
|
Merging, docs said LGTM privately |
Proposed changes
Documentation changes to add information on the Import functionality
Link to any related issue(s): CLOUDP-303586
Type of change:
expected)
Required Checklist:
make fmtand formatted my codeworks in Atlas
Further comments